Hi AndreaKinn,
Reordering in a stream environment is quite costly. AFAIK, Flink doesn't
provide such functions internally.
Watermark is just one of the approaches to deal with the out-of-order
problem. IMO, it just like a coarse-grained
reordering. The late records should be dropped *manually*. M
As mentioned earlier, the watermark is the basis for reasoning about the
overall progression of time. Many operators use the watermark to
correctly organize records, e.g. into the correct time-based window.
Within that window the records may still be unordered. That said, some
operators do take
Thank you, effectively I developed also a simple custom solution for
watermark looking at flink doc but anyway I see unordered printed streams.
I have a doubt about flink behaviour: if I understand, flink doesn't perform
automatically reordering of records in a stream, so if for instance a record
a
, AndreaKinn wrote:
> Hi,
> I'm getting sensor data from a kafka source and I absolutely need they are
> ordered on time data generation basis. I've implemented a custom
> deserialiser and employed an AscendingTimestampExtractor to handle event
> time.
>
Hi,
I'm getting sensor data from a kafka source and I absolutely need they are
ordered on time data generation basis. I've implemented a custom
deserialiser and employed an AscendingTimestampExtractor to handle event
time.
Obviously I set EventTime as streamTimeCharacteristics.
Unfortun
