Watermarks and window firing

[Paul Joireman <pa...@physiq.com>]

Hi all,

The documentation for event timestamps and watermarks (https://ci.apache.org/projects/flink/flink-docs-release-1.1/apis/streaming/event_timestamps_watermarks.html) states that the

The AssignerWithPeriodicWatermarks assigns timestamps and generates watermarks periodically (possibly depending on the stream elements, or purely based on processing time).

The interval (every n milliseconds) in which the watermark will be generated is defined viaExecutionConfig.setAutoWatermarkInterval(...). Each time, the assigner's getCurrentWatermark() method will be called, and a new Watermark will be emitted, if the returned Watermark is non-null and larger than the previous Watermark.

Re: Watermarks and window firing

[Robert Metzger <rm...@apache.org>]

Just for others who are wondering what this email is about: I suspect that
this email was send accidentally and that this is the correct one:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Event-time-watermarks-and-windows-td9687.html

On Mon, Oct 24, 2016 at 4:56 PM, Paul Joireman <pa...@physiq.com>
wrote:

> Hi all,
>
> The documentation for event timestamps and watermarks (
> https://ci.apache.org/projects/flink/flink-docs-
> release-1.1/apis/streaming/event_timestamps_watermarks.html) states that
> the
>
> The AssignerWithPeriodicWatermarks assigns timestamps and generates
> watermarks periodically (possibly depending on the stream elements, or
> purely based on processing time).
>
> The interval (every *n* milliseconds) in which the watermark will be
> generated is defined viaExecutionConfig.setAutoWatermarkInterval(...).
> Each time, the assigner’s getCurrentWatermark() method will be called,
> and a new Watermark will be emitted, if the returned Watermark is non-null
> and larger than the previous Watermark.
>
>
>