Hi Arvid, thank you for the respond. Yeah I tried to run my job shortly after posting my message and I got "State is not supported in rich async function" ;)
I came up with a solution that would solve my initial problem - concurrent/Async problem of processing messages with the same key but unfortunately stet is not sported here. Thank you for the proposition source -> keyby -> map (retrieve state) -> async IO (use state) -> map (update state) However I'm a little bit surprised. I thought that state on a keyed cannot be shared between operators, and here you are suggesting doing that. Is it possible then? Using this occasion I have additional question, Is there any difference from Flink perspective between this two approaches: MyProcessFunction pf = new MyProcessFunction(); MyProcessFunction is stateless object, but it uses Flink keyed state. Setup 1: source -> keyBy(key) -> proces(pf) -> map() -> process(pf) -> sink Setup 2: source -> keyBy(key) -> proces(new MyProcessFunction()) -> map() -> process(new MyProcessFunction()) -> sink -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
