Hello,
savepoint&cancel is in general not an atomic operation, it only
guarantees that no other checkpoint will be completed between the
savepoint and the job cancellation.
You can only guarantee that no messages are sent out if you used a sink
that supports exactly-once, which as far as i k
Hi,
I'm a bit new to Flink and I'm trying to figure out what's the best way to
make an upgrade for my current running topology without having duplicate
messages being sent by the the sink. (One time prior the upgrade and one
time after).
I thought that the "atomic" part of the savepoint & cancel
