The window operator cannot configured to use the max timestamp of the events in the window as the timestamp of the output record. The reason is that such a behavior can produce late records.
If you want to do that, you have to track the max timestamp and assign it yourself with a timestamp assigner. Best, Fabian Am Fr., 3. Mai 2019 um 09:54 Uhr schrieb Averell <lvhu...@gmail.com>: > Thank you Fabian. > > One more question from me on this topic: as I send out early messages in my > window function, the timestamp assigned by window function (to the end-time > of the window) is not like my expectation. I want it to be the time of the > (last) message that triggered the output. > > Is there any way to accomplish that? > Currently, I have an assignTimestampsAndWatermarks after my window > function, > but, as you said, it is against the best practice. > > Thanks and regards, > Averell > > > > -- > Sent from: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ >
