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/job-config-json.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,8 +35,8 @@ The following fields are supported in the *JobConfig.json* file used to [create
35
35
|Name|Type|Required|Value|
36
36
|----|----|--------|-----|
37
37
|DataLocale|string|No|The data locale of the stream analytics job. Value should be the name of a supported. Defaults to 'en-US' if none specified.|
38
-
|OutputErrorPolicy|string|No|Indicates the policy to apply to events that arrive at the output and cannot be written to the external storage due to being malformed (missing column values, column values of wrong type or size). - Stop or Drop|
39
-
|EventsLateArrivalMaxDelayInSeconds|integer|No|The maximum tolerable delay in seconds where events arriving late could be included. Supported range is -1 to 1814399 (20.23:59:59 days) and -1 is used to specify wait indefinitely. If the property is absent, it is interpreted to have a value of -1.|
38
+
|OutputErrorPolicy|string|No|Indicates the policy to apply to events that arrive at the output and can't be written to the external storage due to being malformed (missing column values, column values of wrong type or size). - Stop or Drop|
39
+
|EventsLateArrivalMaxDelayInSeconds|integer|No|The maximum tolerable delay in seconds where events arriving late could be included. Supported range is -1 to 1814399 (20.23:59:59 days) and -1 is used to specify indefinite time. If the property is absent, it's interpreted to have a value of -1.|
40
40
|EventsOutOfOrderMaxDelayInSeconds|integer|No|The maximum tolerable delay in seconds where out-of-order events can be adjusted to be back in order.|
41
41
|EventsOutOfOrderPolicy|string|No|Indicates the policy to apply to events that arrive out of order in the input event stream. - Adjust or Drop|
42
42
|StreamingUnits|integer|Yes|Specifies the number of streaming units that the streaming job uses.|
@@ -45,12 +45,12 @@ The following fields are supported in the *JobConfig.json* file used to [create
45
45
|GlobalStorage.AccountName|string|No|Global storage account is used for storing content related to your stream analytics job, such as SQL reference data snapshots.|
46
46
|GlobalStorage.AccountKey|string|No|Corresponding key for global storage account.|
47
47
|DataSourceCredentialDomain|string|No|Reserved Property for credential local storage.|
48
-
|ScriptType|string|Yes|Reserved property to indicated the type of this source file. Acceptable value is “JobConfig” for JobConfig.json.|
48
+
|ScriptType|string|Yes|Reserved property indicates the type of this source file. Acceptable value is “JobConfig” for JobConfig.json.|
49
49
|Tags|JSON key-value pairs|No|Tags are name/value pairs that enable you to categorize resources and view consolidated billing by applying the same tag to multiple resources and resource groups. Tag names are case-insensitive and tag values are case-sensitive.|
50
50
51
51
## Next steps
52
52
53
53
*[Create an Azure Stream Analytics job in Visual Studio Code](quick-create-visual-studio-code.md)
54
54
*[Test Stream Analytics queries locally with sample data using Visual Studio Code](visual-studio-code-local-run.md)
55
55
*[Test Stream Analytics queries locally against live stream input by using Visual Studio Code](visual-studio-code-local-run-live-input.md)
56
-
*[Deploy an Azure Stream Analytics job using CI/CD npm package](./cicd-overview.md)
56
+
*[Deploy an Azure Stream Analytics job using CI/CD npm package](./cicd-overview.md)
0 commit comments