In the way that FLIP-2 would solve this problem, secondAggregate would ignore
the early firing updates from firstAggregate to prevent double-counting,
correct? If that's the case, I am trying to understand why we'd want to
trigger early-fires every 30 seconds for the secondAggregate if it's only
ac
Hi, I'm interested in helping out on this project. I also want to implement a
continuous time-boxed sliding window, my current use case is a 60-second
sliding window that moves whenever a newer event arrives, discarding any
late events that arrive outside the current window, but *also* re-triggerin
