Aljoschae, exactly.
I'm assuming I don't want to maintain state in the window assigner? What
would you do if you wanted to solve this problem?
On Tue, Aug 16, 2016 at 7:29 AM Aljoscha Krettek
wrote:
> Hi,
> the problem with using session windows is that you don't know which one is
> the "first e
Hi,
the problem with using session windows is that you don't know which one is
the "first element" unless you keep some sort of state in the
WindowAssigner, right? Otherwise, the first element could spawn a window
and the non-first elements could have windows of length 0 that get merged
into the fi
If I'm understanding correctly, you want something liked
"tumbling-session" windows. Session windows [1] do exactly what you
describe but are only evaluated after a certain period of inactivity,
but you want to evaluate the window every X minutes after the first
element for a key arrived, right? I
