Re: Re: Handling "Global" Updating State

2021-05-18 Thread Yun Gao
Recipients:Yun Gao CC:user Subject:Re: Handling "Global" Updating State Hi Yun, That’s very helpful and good to know that the problem/use-case has been thought about. Since my need is probably shorter-term than later, I’ll likely need to explore a workaround. Do you know of an approach

Re: Handling "Global" Updating State

2021-05-17 Thread Rion Williams
inal Mail -- > Sender:Rion Williams > Send Date:Mon May 17 07:00:03 2021 > Recipients:user > Subject:Re: Handling "Global" Updating State >> Hey folks, >> >> After digging into this a bit it does seem like Broadcast State would fit

Re: Re: Handling "Global" Updating State

2021-05-16 Thread Yun Gao
: Handling "Global" Updating State Hey folks, After digging into this a bit it does seem like Broadcast State would fit the bill for this scenario and keeping the downstream operators up-to-date as messages arrived in my Kafka topic. My question is - is there a pattern for pre-populating

Re: Handling "Global" Updating State

2021-05-16 Thread Rion Williams
Hey folks, After digging into this a bit it does seem like Broadcast State would fit the bill for this scenario and keeping the downstream operators up-to-date as messages arrived in my Kafka topic. My question is - is there a pattern for pre-populating the state initially? In my case, I need

Handling "Global" Updating State

2021-05-14 Thread Rion Williams
Hi all, I've encountered a challenge within a Flink job that I'm currently working on. The gist of it is that I have a job that listens to a series of events from a Kafka topic and eventually sinks those down into Postgres via the JDBCSink. A requirement recently came up for the need to filter th