Skip to content

Commit aa7d80b

Browse files
authored
ASA: security scan fix
1 parent af8a690 commit aa7d80b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/stream-analytics/event-ordering.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Your input source (Event Hub/IoT Hub) likely has multiple partitions. Azure Stre
6363

6464
When multiple partitions from the same input stream are combined, the late arrival tolerance is the maximum amount of time that every partition waits for new data. If there's one partition in your event hub or if IoT Hub doesn’t receive inputs, the timeline for that partition doesn't progress until it reaches the late arrival tolerance threshold. This delays your output by the late arrival tolerance threshold. In such cases, you may see the following message:
6565
<br><code>
66-
{"message Time":"2/3/2019 8:54:16 PM UTC","message":"Input Partition [2] does not have additional data for more than [5] minute(s). Partition will not progress until either events arrive or late arrival threshold is met.","type":"InputPartitionNotProgressing","correlation ID":"2328d411-52c7-4100-ba01-1e860c757fc2"}
66+
{"message Time":"2/3/2019 8:54:16 PM UTC","message":"Input Partition [2] does not have additional data for more than [5] minute(s). Partition will not progress until either events arrive or late arrival threshold is met.","type":"InputPartitionNotProgressing","correlation ID":"0000000000-0000-0000-0000-00000000000000"}
6767
</code><br><br>
6868
This message to inform you that at least one partition in your input is empty and will delay your output by the late arrival threshold. To overcome this, it's recommended you either:
6969
1. Ensure all partitions of your Event Hub/IoT Hub receive input.

0 commit comments

Comments
 (0)