Hi, this happens only with Flink 1.5.1? I would expect that in a parallel setting it can happen that a watermark is delayed downstream because the watermark from the other inputs has not caught up yet to "watermark1" (because the watermark at an operator is the minimum of the input watermarks). Could that be the case?
Best, Aljoscha > On 22. Jul 2018, at 22:19, Gyula Fóra <[email protected]> wrote: > > Hi, > In 1.5.1 I have noticed some strange behaviour that happens quite frequently > and I just want to double check with you that this is intended. > > If I have a non-parallel source that takes the following actions: > > emit: event1 > emit: watermark1 > emit: event2 > > it can happen that a downstream operators receives watermark1 after event2. > It doesn't happen very often but definitely seems to happen sometimes. > > Maybe this is a property of the broadcastEmit(..) method but it seems a > little funny :) > > Thanks for the clarification! > > Gyula
