-
>> *From:* Yun Tang
>> *Sent:* Sunday, January 26, 2020 8:42:37 AM
>> *To:* Alexey Trenikhun ; user@flink.apache.org <
>> user@flink.apache.org>
>> *Subject:* Re: Blocking KeyedCoProcessFunction.processElement1
>>
>> Hi Alexey
>>
&
s for new data,
> purge old data etc) in-line with writing stream data to a database
>
> --
> *From:* Yun Tang
> *Sent:* Sunday, January 26, 2020 8:42:37 AM
> *To:* Alexey Trenikhun ; user@flink.apache.org <
> user@flink.apac
possibility of blocking
> processing records.
>
> Best
> Yun Tang
> --
> *From:* Alexey Trenikhun
> *Sent:* Tuesday, January 28, 2020 15:15
> *To:* Yun Tang ; user@flink.apache.org <
> user@flink.apache.org>
> *Subject:* Re: Blo
Tang ; user@flink.apache.org
Subject: Re: Blocking KeyedCoProcessFunction.processElement1
Thank you Yun Tang.
My implementation potentially could block for significant amount of time,
because I wanted to do RDBMS maintenance (create partitions for new data, purge
old data etc) in-line with writing
: Sunday, January 26, 2020 8:42:37 AM
To: Alexey Trenikhun ; user@flink.apache.org
Subject: Re: Blocking KeyedCoProcessFunction.processElement1
Hi Alexey
Actually, I don't understand why you thing
KeyedCoProcessFunction#processElement1 would block for significant amount of
time, it just pr
Hi Alexey
Actually, I don't understand why you thing
KeyedCoProcessFunction#processElement1 would block for significant amount of
time, it just process record from the elements in the first input stream which
is necessary. If you really find it would block for a long time, I think that's
becau
