Skip to content
Advertisement

Azure Stream Analytics Job delayed output of not matching records by 1 minutes between two event hubs

Could anyone help me, why the not matching records are delayed by exactly 1 minutes but the matching records are writing into blog storage container immediately.

Is there any way to avoid the delay even though eventA its not matching with other eventB (being my downstream system will take care in my use-case)

Below is the output but look at the last row (Id:99) currentTime:T19:42:13.1690000Z which delayed by 1 minute compared top 4 rows (currentTime:T19:41:13.1690000Z)

FYI, Sending all the eventA Id (2,4,1,101,99) at once via EventDataBatch via Json serialization

Advertisement

Answer

This is because you use JOIN with DATEDIFF.

The use of temporal joins, such as JOIN with DATEDIFF:

Matches generate as soon as both sides of the matched events arrive.

Data that lacks a match, like LEFT OUTER JOIN, is generated at the end of the DATEDIFF window, for each event on the left side.

More details, you can refer to https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-troubleshoot-output#the-first-output-is-delayed.

User contributions licensed under: CC BY-SA
4 People found this is helpful
Advertisement