|
| 1 | +--- |
| 2 | +title: Azure Data Lake Storage Gen 1 output from Azure Stream Analytics |
| 3 | +description: This article describes Azure Data Lake Storage Gen 1 as an output option for Azure Stream Analytics. |
| 4 | +author: mamccrea |
| 5 | +ms.author: mamccrea |
| 6 | +ms.reviewer: mamccrea |
| 7 | +ms.service: stream-analytics |
| 8 | +ms.topic: conceptual |
| 9 | +ms.date: 08/25/2020 |
| 10 | +--- |
| 11 | + |
| 12 | +# Azure Data Lake Storage Gen 1 output from Azure Stream Analytics |
| 13 | + |
| 14 | +Stream Analytics supports [Azure Data Lake Storage Gen 1](../data-lake-store/data-lake-store-overview.md) outputs. Azure Data Lake Storage is an enterprise-wide, hyperscale repository for big data analytic workloads. You can use Data Lake Storage to store data of any size, type, and ingestion speed for operational and exploratory analytics. Stream Analytics needs to be authorized to access Data Lake Storage. |
| 15 | + |
| 16 | +Azure Data Lake Storage output from Stream Analytics is not available in the Azure China 21Vianet and Azure Germany (T-Systems International) regions. |
| 17 | + |
| 18 | +## Output configuration |
| 19 | + |
| 20 | +The following table lists property names and their descriptions to configure your Data Lake Storage Gen 1 output. |
| 21 | + |
| 22 | +| Property name | Description | |
| 23 | +| --- | --- | |
| 24 | +| Output alias | A friendly name used in queries to direct the query output to Data Lake Store. | |
| 25 | +| Subscription | The subscription that contains your Azure Data Lake Storage account. | |
| 26 | +| Account name | The name of the Data Lake Store account where you're sending your output. You're presented with a drop-down list of Data Lake Store accounts that are available in your subscription. | |
| 27 | +| Path prefix pattern | The file path that's used to write your files within the specified Data Lake Store account. You can specify one or more instances of the {date} and {time} variables:<br /><ul><li>Example 1: folder1/logs/{date}/{time}</li><li>Example 2: folder1/logs/{date}</li></ul><br />The time stamp of the created folder structure follows UTC and not local time.<br /><br />If the file path pattern doesn't contain a trailing slash (/), the last pattern in the file path is treated as a file name prefix. <br /><br />New files are created in these circumstances:<ul><li>Change in output schema</li><li>External or internal restart of a job</li></ul> | |
| 28 | +| Date format | Optional. If the date token is used in the prefix path, you can select the date format in which your files are organized. Example: YYYY/MM/DD | |
| 29 | +|Time format | Optional. If the time token is used in the prefix path, specify the time format in which your files are organized. Currently the only supported value is HH. | |
| 30 | +| Event serialization format | The serialization format for output data. JSON, CSV, and Avro are supported.| |
| 31 | +| Encoding | If you're using CSV or JSON format, an encoding must be specified. UTF-8 is the only supported encoding format at this time.| |
| 32 | +| Delimiter | Applicable only for CSV serialization. Stream Analytics supports a number of common delimiters for serializing CSV data. Supported values are comma, semicolon, space, tab, and vertical bar.| |
| 33 | +| Format | Applicable only for JSON serialization. **Line separated** specifies that the output is formatted by having each JSON object separated by a new line. If you select **Line separated**, the JSON is read one object at a time. The whole content by itself would not be a valid JSON. **Array** specifies that the output is formatted as an array of JSON objects. This array is closed only when the job stops or Stream Analytics has moved on to the next time window. In general, it's preferable to use line-separated JSON, because it doesn't require any special handling while the output file is still being written to.| |
| 34 | +| Authentication mode | You can authorize access to your Data Lake Storage account using [Managed Identity](stream-analytics-managed-identities-adls.md) or User token. Once you grant access, you can revoke access by changing the user account password, deleting the Data Lake Storage output for this job, or deleting the Stream Analytics job. | |
| 35 | + |
| 36 | +## Partitioning |
| 37 | + |
| 38 | +For the partition key, use {date} and {time} tokens in the path prefix pattern. Choose a date format, such as YYYY/MM/DD, DD/MM/YYYY, or MM-DD-YYYY. Use HH for the time format. The number of output writers follows the input partitioning for [fully parallelizable queries](stream-analytics-scale-jobs.md). |
| 39 | + |
| 40 | +## Output batch size |
| 41 | + |
| 42 | +For the maximum message size, see [Data Lake Storage limits](../azure-resource-manager/management/azure-subscription-service-limits.md#data-lake-store-limits). To optimize batch size, use up to 4 MB per write operation. |
| 43 | + |
| 44 | +## Next steps |
| 45 | + |
| 46 | +* [Quickstart: Create a Stream Analytics job by using the Azure portal](stream-analytics-quick-create-portal.md) |
| 47 | +* [Quickstart: Create an Azure Stream Analytics job using the Azure CLI](quick-create-azure-cli.md) |
| 48 | +* [Quickstart: Create an Azure Stream Analytics job by using an ARM template](quick-create-azure-resource-manager.md) |
| 49 | +* [Quickstart: Create a Stream Analytics job using Azure PowerShell](stream-analytics-quick-create-powershell.md) |
| 50 | +* [Quickstart: Create an Azure Stream Analytics job by using Visual Studio](stream-analytics-quick-create-vs.md) |
| 51 | +* [Quickstart: Create an Azure Stream Analytics job in Visual Studio Code](quick-create-vs-code.md) |
0 commit comments