Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1341#issuecomment-155785654
I think this breaks the checkpoint atomicity. The fetcher (which emits the
data to the source context) will not lock on the checkpoint lock any more, but
on an arbitrary new object created by the offset committer.
Why can't the offset committer simply use the checkpoint lock? Blocking the
checkpoint lock for an `Arrays.copyOfRange()` call seems pretty okay.
---
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.
---
