Additional fix of same bug for out-of-order tuples outside of allowed lateness before any watermark occurred. Then, tuples with a timestamp < startsTsOfFirstSlice or timestamp < timestampOfFirstTuple - maxLateness are outside of allowed lateness and are discarded.
For context-ware windows (e.g. session window), a new slice is added with an addModification, if the out-of-order tuple is still in the allowed lateness and starts a new window.
Fixes https://github.com/TU-Berlin-DIMA/scotty-window-processor/issues/44 to not process out-of-order tuples outside of the allowed lateness (i.e. with a
timestamp < currentWatermark - maxLateness - maxFixedWindowSize).Additional fix of same bug for out-of-order tuples outside of allowed lateness before any watermark occurred. Then, tuples with a
timestamp < startsTsOfFirstSliceortimestamp < timestampOfFirstTuple - maxLatenessare outside of allowed lateness and are discarded.For context-ware windows (e.g. session window), a new slice is added with an addModification, if the out-of-order tuple is still in the allowed lateness and starts a new window.