Extending on what Paris said:
If you have an exactly-once sink (like the Rolling/Bucketing file sink or
the Cassandra write-ahead sink), then all of them are correctly adjusted to
preserve the exactly once semantics. That is regardless or one, two, or n
sinks.
On Thu, Jan 5, 2017 at 2:47 PM, Pari
Hi Nancy,
Flink’s vanilla rollback recovery mechanism restarts computation from a global
checkpoint thus sink duplicates (job output) can occur no matter how many sinks
are declared; the whole computation in the failed execution graph will roll
back.
cheers
Paris
> On 5 Jan 2017, at 14:24,
