That makes sense, thank you, Hequn. I can see the tradeoff between using
allowedLateness on a window to trigger multiple firings, versus a window
with a watermark lagging some amount of time (e.g. 3 hours) that has only a
single firing.
Thanks again,
--
Scott Kidder
On Fri, Oct 19, 2018 at 7:51
Hi Scott,
Yes, the window trigger firing for every single late element.
If you only want the window to be triggered once, you can:
- Remove the allowedLateness()
- Use BoundedOutOfOrdernessTimestampExtractor to emit Watermarks that
lag behind the element.
The code(scala) looks like:
> c
I'm using event-time windows of 1 hour that have an allowed lateness of
several hours. This supports the processing of access logs that can be
delayed by several hours. The windows aggregate data over the 1 hour period
and write to a database sink. Pretty straightforward.
Will the event-time trigg
