Github user zhenzhongxu commented on the issue:
https://github.com/apache/flink/pull/4149
Hi @tzulitai. Yes, we do have a use case where we need to disable Flink
checkpointing because the time interval checkpointing model does not work with
our constraints. We had to trigger Kafka commits by manually taking offset
snapshot and commit after sink flushes (parallel source/sink operators are
chained together), in this case, the partition offset is not incremented until
the thread exits sink operator logic. Now, the only way to make the commit
accurate is to expose which partition the in-flight message belongs to and we
can consciously +1 to the offset at the time of snapshoting.
---
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.
---
