[
https://issues.apache.org/jira/browse/FLINK-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147549#comment-15147549
]
ASF GitHub Bot commented on FLINK-3332:
---------------------------------------
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/1640#issuecomment-184284513
Great addition. But in my personal opinion it's not a good idea to name the
sink exactly once when you say: *Note that a job failure while the data is
being committed will cause duplicate data to be committed, but the chance of
this happening is much smaller than for a naive At-Least-once implementation.*
What do others sink (I'll leave this typo... :smile:)?
> 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)
