Hi,

I am looking at the implementation of  RowTimeBoundedRangeOver (in the context 
of Stream SQL). I see that the logic is that the progress happens based on the 
timestamps of the rowevent - i.e., when an even arrives we register to be 
processed based on it's timestamp 
(ctx.timerService.registerEventTimeTimer(triggeringTs))

In the onTimer we remove (retract) data that has expired. However, we do not 
consider watermarks nor some allowed latency for the events or anything like 
this, which makes me ask:
Don't we need to work with watermarks when we deal with even time? And keep the 
events within the allowed delayed/next watermark?  Am I missing something? Or 
maybe we do not consider at this point allowedLateness  for this version?

Thanks

Best regards,

Reply via email to