Indeed you are unfortunately right. Triggers do not define/control lifecycle of
the window, so it could happen that each new event is constantly pushing the
leading boundary of the window, while your custom trigger is constantly
triggering and purging this single EVENT (because exceeded max
Thanks you for the response.
I would not mind the second scenario as in a second window, which
your illustration suggests with a custom trigger approach, I am not
certain though that triggers define the lifecycle of a window, as in a
trigger firing does not necessarily imply a Garbage
It might be more complicated if you want to take into account events coming in
out of order. For example you limit length of window to 5 and you get the
following events:
1 2 3 4 6 7 8 5
Do you want to emit windows:
[1 2 3 4 5] (length limit exceeded) + [6 7 8] ?
Or are you fine with
I am implementing a bounded session window but I require to short circuit
the session if the session length ( in count of events or time ) go beyond
a configured limit , a very reasonable scenario ( bot etc ) . I am using
the approach as listed. I am not sure though if the Window itself is being
