You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/stream-analytics/stream-analytics-documentdb-output.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.custom: seodec18
13
13
# Azure Stream Analytics output to Azure Cosmos DB
14
14
Azure Stream Analytics can target [Azure Cosmos DB](https://azure.microsoft.com/services/documentdb/) for JSON output, enabling data archiving and low-latency queries on unstructured JSON data. This document covers some best practices for implementing this configuration.
15
15
16
-
If you're unfamiliar with Azure Cosmos DB, see the [Azure Cosmos DB learning path](https://azure.microsoft.com/documentation/learning-paths/documentdb/) to get started.
16
+
If you're unfamiliar with Azure Cosmos DB, see the [Azure Cosmos DB documentation](https://docs.microsoft.com/azure/cosmos-db/) to get started.
17
17
18
18
> [!Note]
19
19
> At this time, Stream Analytics supports connection to Azure Cosmos DB only through the *SQL API*.
@@ -59,7 +59,7 @@ If you want to save *all* documents, including the ones that have a duplicate ID
59
59
Azure Cosmos DB automatically scales partitions based on your workload. So we recommend [unlimited](../cosmos-db/partition-data.md) containers as the approach for partitioning your data. When Stream Analytics writes to unlimited containers, it uses as many parallel writers as the previous query step or input partitioning scheme.
60
60
61
61
> [!NOTE]
62
-
> At this time, Azure Stream Analytics supports only unlimited containers with partition keys at the top level. For example, **/region** is supported. Nested partition keys (for example, **/region/name**) are not supported.
62
+
> At this time, Azure Stream Analytics supports only unlimited containers with partition keys at the top level. For example, `/region` is supported. Nested partition keys (for example, `/region/name`) are not supported.
63
63
64
64
Depending on your choice of partition key, you might receive this _warning_:
65
65
@@ -107,7 +107,7 @@ Using Azure Cosmos DB as an output in Stream Analytics generates the following p
107
107
|Account ID | The name or endpoint URI of the Azure Cosmos DB account.|
108
108
|Account key | The shared access key for the Azure Cosmos DB account.|
109
109
|Database | The Azure Cosmos DB database name.|
110
-
|Collection name pattern | The container name. `MyContainer` is a sample valid input. One container named `MyContainer` must exist. |
110
+
|Container name | The container name, such as `MyContainer`. One container named `MyContainer` must exist. |
111
111
|Document ID | Optional. The column name in output events used as the unique key on which insert or update operations must be based. If you leave it empty, all events will be inserted, with no update option.|
112
112
113
113
After you configure the Azure Cosmos DB output, you can use it in the query as the target of an [INTO statement](https://docs.microsoft.com/stream-analytics-query/into-azure-stream-analytics). When you're using an Azure Cosmos DB output that way, [a partition key needs to be set explicitly](https://docs.microsoft.com/azure/stream-analytics/stream-analytics-parallelization#partitions-in-sources-and-sinks).
0 commit comments