my surprise I found out that the tumbling window operator has no
> effect on the watermarks of the resulting append stream - the watermarks of
> the input stream are propagated as-is.
>
> This seems to be a documented behavior
> https://ci.apache.org/projects/flink/flink-docs-stable/
found out that the tumbling window operator has no
> effect on the watermarks of the resulting append stream - the watermarks of
> the input stream are propagated as-is.
>
> This seems to be a documented behavior
> https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/operators/wi
.html#interaction-of-watermarks-and-windows
but
it's still very counter-intuitive to me and I couldn't find any explanation
of it.
My understanding of the watermarking is that MOST data is expected to
arrive with event time below the stream's watermark. Late events are either
discarded or sho
