Re: Finite source without blocking save-points

2019-11-04 Thread bupt_ljy
: user Date: Monday, Nov 4, 2019 23:41 Subject: Re: Finite source without blocking save-points Hi Jiayi, This would allow me to call the Kafka producer without risking a race condition, but it comes with its own problem: unless the source has a parallelism of 1, it will trigger multiple times. I

Re: Finite source without blocking save-points

2019-11-04 Thread Gaël Renoux
s you’ve already had a rules source > and you can send rules in #open function for a startup if your rules source > inherit from #RichParallelSourceFunction. > > > Best, > > Jiayi Liao > > Original Message > *Sender:* Gaël Renoux > *Recipient:* user > *Date:* Mo

Re: Finite source without blocking save-points

2019-11-04 Thread bupt_ljy
Original Message Sender: Gaël Renoux Recipient: user Date: Monday, Nov 4, 2019 22:50 Subject: Finite source without blocking save-points Hello everyone, I have a job which runs continuously, but it also needs to send a single specific Kafka message on startup. I tried the obvious approach to

Finite source without blocking save-points

2019-11-04 Thread Gaël Renoux
Hello everyone, I have a job which runs continuously, but it also needs to send a single specific Kafka message on startup. I tried the obvious approach to use StreamExecutionEnvironment.fromElements and add a Kafka sink, however that's not possible: the source being finished, it becomes impossibl