Kyle Godfrey
05/23/2023, 5:09 PMFIRE_AND_PURGE
to the next global window instead of the event being the last event in the global window that it’s closing. It looks like an evictor might be able to do this but the stipulation that an evictor requires all events to stay in state until the window is closed and the evictor run isn’t feasible (we’re aggregating data for thousands of assets, each with thousands of events for each asset so it’s just too much state to keep). Is there another way of pushing this event off to the next window?