[
https://issues.apache.org/jira/browse/FLINK-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148456#comment-15148456
]
ASF GitHub Bot commented on FLINK-3332:
---------------------------------------
Github user zentol commented on a diff in the pull request:
https://github.com/apache/flink/pull/1640#discussion_r52995692
--- Diff: docs/apis/streaming/fault_tolerance.md ---
@@ -176,6 +176,11 @@ state updates) of Flink coupled with bundled sinks:
<td></td>
</tr>
<tr>
+ <td>Cassandra sink</td>
+ <td>exactly once</td>
--- End diff --
which is also not true. a flink failure while data is being written to
cassandra will cause duplicates. you can only say this if writing the data to
the final table is completely handled by cassandra (for example by writing into
a temporary table, exporting it to csv and importing into the target table; the
only way for duplicates is if cassandra fails while importing).
> Provide an exactly-once Cassandra connector
> -------------------------------------------
>
> Key: FLINK-3332
> URL: https://issues.apache.org/jira/browse/FLINK-3332
> Project: Flink
> Issue Type: Improvement
> Components: Streaming Connectors
> Reporter: Robert Metzger
> Assignee: Chesnay Schepler
>
> With FLINK-3311, we are adding a Cassandra connector to Flink.
> It would be good to also provide an "exactly-once" C* connector.
> I would like to first discuss how we are going to implement this in Flink.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
