FIRE and FIRE_AND_PURGE still have the same meaning.
So on eventTime, when your trigger says FIRE_AND_PURGE, your window will be
evaluated (4) and its state will be purged. Now, when the red circle arrives,
will be empty, so if the onElement says FIRE, the result will be 1.
If you want to keep also the previous elements and have
4 on the onEventTime, and 5 onElement for the red circle, then you just
have to modify your trigger to return FIRE onEventTime, instead of
When the allowed lateness expires, your window will be garbage collected
(all its state will be purged). So your trigger does not need to worry about
I hope this answers your question.
> On Oct 13, 2016, at 4:16 PM, swiesman <swies...@mediamath.com> wrote:
> Hi all,
> I have a question about allowed lateness semantics and window state. I have
> a custom event time trigger that does an early FIRE onElement for a certain
> set of conditions and then a FIRE_AND_PURGE onEventTime.
> And this has worked great for me. However I now want to add a certain amount
> of allowed lateness to this window. My understanding has been that when
> TriggerResult.FIRE_AND_PURGE is returned the window will be fully evaluated
> and the state cleared. So if a new element shows up in the allowed lateness
> time will it be put into a new singleton window and evaluated or does
> specifying allowed lateness defer the window purge until after the allowed
> lateness has passed?
> Put another way, in the illustration below if my window is counting circles
> after the red circle is seen will my window output 5 or 1? If I want it to
> output 5 do I have to modify my trigger?
> Thank you,
> Seth Wiesman
> View this message in context:
> Sent from the Apache Flink User Mailing List archive. mailing list archive at