Re: BoundedOutOfOrdernessTimestampExtractor and allowedlateness

2016-10-17 Thread Yassine MARZOUGUI
Hi Fabian, Thank you very much for the great answer and example, I appreciate it! It is all clear now. Best, Yassine 2016-10-17 16:29 GMT+02:00 Fabian Hueske : > I have to extend my answer: > > The behavior allowedLateness that I described applies only if the window > trigger calls FIRE when th

Re: BoundedOutOfOrdernessTimestampExtractor and allowedlateness

2016-10-17 Thread Fabian Hueske
I have to extend my answer: The behavior allowedLateness that I described applies only if the window trigger calls FIRE when the window is evaluated (this is the default behavior of most triggers). In case the trigger calls FIRE_AND_PURGE, the state of the window is purged when the function is ev

Re: BoundedOutOfOrdernessTimestampExtractor and allowedlateness

2016-10-17 Thread Fabian Hueske
Hi Yassine, the difference is the following: 1) The BoundedOutOfOrdernessTimestampExtractor is a built-in timestamp extractor and watermark assigner. A timestamp extractor tells Flink when an event happened, i.e., it extracts a timestamp from the event. A watermark assigner tells Flink what the c

BoundedOutOfOrdernessTimestampExtractor and allowedlateness

2016-10-17 Thread Yassine MARZOUGUI
Hi, I'm a bit confused about how Flink deals with late elements after the introduction of allowedlateness to windows. What is the difference between using a BoundedOutOfOrdernessTimestampExtractor(Time.seconds(X)) and allowedlateness(Time.seconds(X))? What if one is used and the other is not? and