Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/3278
@tillrohrmann
Yes, in the condition that you described, then at-least-once doesn't hold.
I said _might_ mainly considering there is chance that for every checkpoint
barrier, the previous events (i.e. `event1` in your example) has been
committed. But yes, essentially this indeterminate behaviour means that it is
not at-least-once, so I'm incorrect in saying that it _might_.
I was trying to point out that this indeterminate behaviour made it hard to
have a stable test for `testAtLeastOnceProducerFailsIfFlushingDisabled()`
without relying on sleeping, which ultimately leads to flaky tests.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
