Skip to content

Commit 6176c31

Browse files
Update time-series-insights-update-how-to-shape-events.md
1 parent 7e4eae5 commit 6176c31

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/time-series-insights/time-series-insights-update-how-to-shape-events.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.workload: big-data
88
ms.service: time-series-insights
99
services: time-series-insights
1010
ms.topic: conceptual
11-
ms.date: 02/14/2020
11+
ms.date: 02/24/2020
1212
ms.custom: seodec18
1313
---
1414

@@ -35,7 +35,7 @@ For the best query performance, adhere to the following rules of thumb:
3535

3636
## Column flattening
3737

38-
During ingestion, payloads that contain nested columns (attributes) will be flattened so that the column name is a single value with a delineator.
38+
During ingestion, payloads that contain nested objects will be flattened so that the column name is a single value with a delineator.
3939

4040
* For example, the following nested JSON:
4141

@@ -104,7 +104,7 @@ There's a single Azure IoT Hub message sent where the outer array contains a sha
104104
Let's take a closer look at how to use [Time Series Instance](./time-series-insights-update-tsm.md#time-series-model-instances) to shape your JSON more optimally.
105105

106106
> [!NOTE]
107-
> The [Time Series IDs](./time-series-insights-update-how-to-id.md) below *deviceIds*.
107+
> The [Time Series IDs](./time-series-insights-update-how-to-id.md) below are *deviceIds*.
108108
109109
```JSON
110110
[
@@ -139,7 +139,7 @@ Let's take a closer look at how to use [Time Series Instance](./time-series-insi
139139
]
140140
```
141141

142-
Time Series Insights Preview joins a table (after flattening) during query time. The table includes additional columns, such as **Type**. The following example demonstrates [how you can shape](./time-series-insights-send-events.md#supported-json-shapes) your telemetry data.
142+
Time Series Insights Preview joins a table (after flattening) during query time. The table includes additional columns, such as **Type**.
143143

144144
| deviceId | Type | L1 | L2 | timestamp | series_Flow Rate ft3/s | series_Engine Oil Pressure psi |
145145
| ---- | ---- | ---- | ---- | ---- | ---- | ---- |
@@ -188,6 +188,6 @@ In this case, the *latest* property value would overwrite the earlier one.
188188
189189
## Next steps
190190

191-
* Read [Azure Time Series Insights Preview query syntax](https://docs.microsoft.com/rest/api/time-series-insights/preview#time-series-expression-and-syntax) to send well-shaped JSON to the [Preview APIs](https://docs.microsoft.com/rest/api/time-series-insights/preview).
191+
* To put these guidelines into practice, read [Azure Time Series Insights Preview query syntax](./time-series-insights-query-data-csharp.md). You'll learn more about the query syntax for the Time Series Insights [Preview REST API](https://docs.microsoft.com/rest/api/time-series-insights/preview) for data access.
192192

193193
* Combine JSON best practices with [How to Time Series Model](./time-series-insights-update-how-to-tsm.md).

0 commit comments

Comments
 (0)