Thank you for the clarification! After some discussion, I think we'll be
using processing time as an alternative for our use case.
Just for my education, if I really need ingestion-time. It seem like I can
get it by either of the below approach?
// 1. an ingestion time watermark strategy
new Wat
Hi,
IngestionTime is usually used when the records don't have a proper event
time associated with it, but the job has a long topology, and users want to
persist the (time)order of events as they arrive in the system.
In that sense, you can use the regular event time watermark strategies also
for i
Hi,
Since *TimeCharacteristic,* is deprecated.
AFAIK,
- TimeCharacteristic*.*ProcessingTime -> WatermarkStrategy.noWatermarks()
- TimeCharacteristic*.*EventTime ->
WatermarkStrategy.forBoundedOutOfOrderness()
- TimeCharacteristic*.*IngestionTime -> ???
Do we have a built-in *WatermarkStrategy *e
