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:)?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
