You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2016/01/27 16:23:39 UTC
[jira] [Commented] (FLINK-3294) KafkaConsumer (0.8) commit offsets
using SimpleConsumer.commitOffsets()
[ https://issues.apache.org/jira/browse/FLINK-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119441#comment-15119441 ]
Robert Metzger commented on FLINK-3294:
---------------------------------------
I hacked a first approach to this here: https://github.com/rmetzger/flink/tree/yangjun_fix
I'm not sure if I'm going to complete this any time soon.
If users are interested in this, please let me know (by writing a comment into the JIRA).
> KafkaConsumer (0.8) commit offsets using SimpleConsumer.commitOffsets()
> -----------------------------------------------------------------------
>
> Key: FLINK-3294
> URL: https://issues.apache.org/jira/browse/FLINK-3294
> Project: Flink
> Issue Type: Bug
> Components: Kafka Connector
> Reporter: Robert Metzger
>
> Currently, the 0.8 consumer for Kafka is committing the offsets manually into Zookeeper so that users can track the lag using external tools.
> The 0.8 consumer has a pluggable design, and this component is easily pluggable.
> Since OffsetCommitRequest version=1 (supported in 0.8.2 or later), users can choose between two offset commit modes:
> a) Let the broker commit into ZK (this is what we are doing from the consumer
> b) Let the broker commit the offset into a special topic.
> By adding a different "OffsetHandler" backend, users can commit offsets from the brokers (reducing the total number of ZK connections) or into the broker's offset topic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)