Re: WatermarkStrategy for IngestionTime

gt; Afaik ingestion time is rarely used in practice. > > On Tue, Apr 5, 2022 at 12:10 AM Xinbin Huang wrote: > >> Hi, >> >> Since *TimeCharacteristic,* is deprecated. >> >> AFAIK, >> - TimeCharacteristic*.*ProcessingTime -&

WatermarkStrategy for IngestionTime

Hi, Since *TimeCharacteristic,* is deprecated. AFAIK, - TimeCharacteristic*.*ProcessingTime -> WatermarkStrategy.noWatermarks() - TimeCharacteristic*.*EventTime -> WatermarkStrategy.forBoundedOutOfOrderness() - TimeCharacteristic*.*IngestionTime -> ??? Do we have a built-in *WatermarkStrategy

Temporarily pause splits fetching when unavailable

Hi, I'm building a custom source that reads from a distributed event queue, similar to Pulsar or Kafka. One interesting characteristic of this event queue is that some partitions may temporarily become unavailable (i.e. a few hours). And it'll need to resume from the previous progress when the

Approach to test custom Source/Sink

Hi team, I'm currently implementing a custom source and sink, and I'm trying to find a way to test these implementations. The testing section in the

Custom Source with the new Data Source API

Hi team, I'm trying to develop a custom source using the new Data Source API but I have some hard time finding examples for it. Can you point me to some existing Sources implemented with the new Data Source API? It would be ideal if source is for a pull-based unbound source (i.e. Kafka). Thanks!

Organizing Flink Applications: Mono repo or polyrepo

Hi community I am curious about people's experience in structuring Flink applications. Do you use a mono repo structure (multiple applications in one single repo) or broken down each application into its own repo? If possible, can you share some of your thoughts on the pros/cons of each