Yeah, unless I am misunderstanding something. The output from my repro code shows event timestamp and the context timestamp every time we process an event.
Receiving event at: 2000-01-01T00:00:00.000Z Resetting timer to : 2000-01-01T00:15:00.000Z Receiving event at: 2000-01-01T00:05:00.000Z Resetting timer to : 2000-01-01T00:20:00.000Z <-- Shouldn’t the timer have fired before we processed the next event? Receiving event at: 2000-01-01T00:40:00.000Z Why didnt the timer fire? Resetting timer to : 2000-01-01T00:55:00.000Z Receiving event at: 2000-01-01T00:45:00.000Z Resetting timer to : 2000-01-01T01:00:00.000Z Receiving event at: 2000-01-01T00:50:00.000Z Resetting timer to : 2000-01-01T01:05:00.000Z Timer firing at: 2000-01-01T01:05:00.000Z From: Reuven Lax <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Monday, August 3, 2020 at 10:02 AM To: dev <[email protected]> Subject: Re: Stateful Pardo Question Notice: This email is from an external sender. Are you sure that there is a 15 minute gap in your data? On Mon, Aug 3, 2020 at 6:20 AM [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> wrote: I am confused about the behavior of timers on a simple stateful pardo. I have put together a little repro here: https://github.com/randomsamples/pardo_repro I basically want to build something like a session window, accumulating events until quiescence of the stream for a given key and gap time, then output results. But it appears that the timer is not firing when the watermark is passed it expiration time, so the event stream is not being split as I would have expected. Would love some help getting this work, the behavior is for a project I’m working on.
