Re: Watermark behavior when connecting streams

2021-12-02 Thread David Morávek
t; > https://nightlies.apache.org/flink/flink-docs-master/docs/dev/datastream/operators/windows/#consecutive-windowed-operations > > > > Regards, > > Alexis. > > > > *From:* David Morávek > *Sent:* Donnerstag, 2. Dezember 2021 17:26 > *To:* Alexis Sarda-Espinosa

RE: Watermark behavior when connecting streams

2021-12-02 Thread Alexis Sarda-Espinosa
://nightlies.apache.org/flink/flink-docs-master/docs/dev/datastream/operators/windows/#consecutive-windowed-operations Regards, Alexis. From: David Morávek Sent: Donnerstag, 2. Dezember 2021 17:26 To: Alexis Sarda-Espinosa Cc: user@flink.apache.org Subject: Re: Watermark behavior when connecting streams

Re: Watermark behavior when connecting streams

2021-12-02 Thread David Morávek
Hi Alexis, please take a look at AbstractStreamOperator [1] for details how the watermark is calculate for TwoInputOperator. It uses pretty much the same approach as for with the single input one (it simply takes a minimum). For watermark re-assignment, we ignore input watermark unless it's Long.

Watermark behavior when connecting streams

2021-12-01 Thread Alexis Sarda-Espinosa
Hi everyone, Based on what I know, a single operator with parallelism > 1 checks the watermarks from all its streams and uses the smallest one out of the non-idle streams. My first question is whether watermarks are forwarded as long as a different watermark strategy is not applied downstream?