That is correct, the window operator happily accepts late elements into the applicable window(s). Though the element is late (with respect to the current watermark) it might still be included in the main firing, or provoke a late firing.
Elements occurring downstream of an operator that uses late firing must undergo de-duplication by whatever means. Other solutions: leverage the side output feature of the window operator, or be more conservative with your watermarks (decreasing complexity at the expense of latency). -Eron On Fri, Dec 22, 2017 at 3:59 PM, Jagadish <jagadish1...@gmail.com> wrote: > Thanks for the super-helpful reply! > > Would the late-firing from the "hourly" window be considered an on-time > arrival for the subsequent "daily" window operator? Since, its windowing > duration is much longer (1 day), I'd expect the "on-time/default" result > emitted from the "daily" window to include the late-firings previous hourly > windows? > > > > -- > Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/ >
