Github user wanderingbort commented on the pull request:
https://github.com/apache/flink/pull/1690#issuecomment-207065222
I just wanted to echo @StephanEwen 's sentiment.
Flink's management of offsets seems to supersede the Kafka concept of
committed offsets (whether to ZK or an 0.9 broker) leaving me to think there
are only 2 scenarios where offset commitment is useful in the context of flink :
- coordinating with delivery with consumers outside the flink ecosystem
(which seems conceptually dubious)
- reporting to monitoring software that understands 0.8- zookeeper stored
offsets or 0.9+ broker stored offsets
I would consider both of these to be optional features and not required
features.
For my particular use case, we are on Kafka 0.8 and requiring write access
to the zookeeper cluster that is coordinating kafka in order to access
read-only message data is problematic.
---
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.
---
