Hi Kant,according to the documentation [1], you don't need to set a watermark assigner:Compared to event time, ingestion time programs cannot handle any out-of-order events or late data, but the programs don’t have to specify how to generate watermarks.
Internally, ingestion time is treated much like event time, but with automatic timestamp assignment and automatic watermark generation.
So it's neither possible to assign timestamps nor watermark, but it seems as if the default behavior is exactly as you want it to be. If that doesn't work for you, could you please rephrase your last question or describe your use case? I didn't get it.On Tue, Mar 10, 2020 at 5:01 AM kant kodali <[hidden email]> wrote:Hi All,
Do I need to set assignTimestampsAndWatermarks if I set my time characteristic to IngestionTime?say I set my time characteristic of stream execution environment to Ingestion time as follows
streamExecutionEnvironment.setStreamTimeCharacteristic(TimeCharacteristic.IngestionTime);
do I need to call
datastream.assignTimestampsAndWatermarks(AscendingTimestampExtractor)
?I thought
datastream.assignTimestampsAndWatermarks
is mandatory only if time characteristic is event time. No? Did this behavior change in Flink 1.10? because I see libraries not setting datastream.assignTimestampsAndWatermarks when time characteristic is Ingestion time but they do for event time. If not, I am wondering how can I setAscendingTimestampExtractor
in a distributed environment? is there anyway to add monotonically increasing long(AscendingTimestampExtractor) without any distributed locks?Thanks!
Free forum by Nabble | Edit this page |