Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/4454
@pnowojski adding a link to `TwoPhaseCommitSinkFunctionTest` might make
sense for testing exactly-once delivery.
There are also often cases where the user, in particular, wants to check
that their operator state semantics are exactly-once.
However, I think we can also wait on other's opinions on whether or not
this information is really required. Instructions for watermark / timestamp
testing makes sense because that's something users frequently mess up with
incorrect extractor implementations. Exactly-once semantics, however, isn't
something the user scope can touch.
I'm mentioning it because we sometimes have users in the mailing lists
testing exactly-once incorrectly (maybe also because they misunderstood some
concepts) and asking.
---
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.
---
