Re: End-to-end exactly-once semantics in simple streaming app

not viable. regards Patrick -- Patrick Fial Client Platform Entwickler Information Design One AG Phone +49 69 244 502 38 Web www.id1.de <http://www.id1.de/> Information Design One AG, Baseler Straße 10, 60329 Frankfurt am Main Registereintrag: Amtsgericht Frankfurt am Main, HRB

Re: End-to-end exactly-once semantics in simple streaming app

, given the logic described in my original post, the database access is never going to be idempotent, which lies in the nature of the required insert/update logic. regards Patrick -- Patrick Fial Client Platform Entwickler Information Design One AG Phone +49 69 244 502 38 Web www.id1.de

End-to-end exactly-once semantics in simple streaming app

. Thanks in advance for any help. best regards Patrick Fial -- Patrick Fial Client Platform Entwickler Information Design One AG Phone +49 69 244 502 38 Web www.id1.de <http://www.id1.de/> Information Design One AG, Baseler Straße 10, 60329 Frankfurt am Main Registereintrag: Amtsg

Manual error/recovery handling in flink applications

checkpoints However, searching the docs, I fail to see how either of those could be used in the middle of stream processing from within a single operator. So, what would be the recommended strategies for fine-grained error handling and recovery in a streaming application? -- Patrick Fial Client

Maintaining message input order in streams with keyBy/filter/connect

rder. But this is not the case. I don't know at which point in code the order gets messed up, or how those operations are distributed amongst threads, so I don't know how to solve this issue. Best regards Patrick Fial