[
https://issues.apache.org/jira/browse/KAFKA-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Liquan Pei updated KAFKA-3462:
------------------------------
Description: SinkTasks should be able to disable consumer offset commit if
they manage offsets in the sink data store rather than using Kafka consumer
offsets. For example, an HDFS connector might record offsets in HDFS to
provide exactly once delivery. When the SinkTask is started or a rebalance
occurs, the task would reload offsets from HDFS. In this case, disabling
consumer offset commit will save some CPU cycles and network IOs. (was:
SinkTasks should be able to disable consumer offset commit if they manage
offsets in the sink data store rather than using Kafka consumer offsets. For
example, an HDFS connector might record offsets in HDFS to provide exactly once
delivery. When the SinkTask is started or a rebalance occurs, the task
would reload offsets from HDFS. In this case, disabling consumer offset commit
will save some CPU cycles and network IOs.)
> Allow SinkTasks to disable consumer offset commit
> --------------------------------------------------
>
> Key: KAFKA-3462
> URL: https://issues.apache.org/jira/browse/KAFKA-3462
> Project: Kafka
> Issue Type: Bug
> Components: copycat
> Affects Versions: 0.10.1.0
> Reporter: Liquan Pei
> Assignee: Liquan Pei
> Priority: Minor
> Fix For: 0.10.1.0
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> SinkTasks should be able to disable consumer offset commit if they manage
> offsets in the sink data store rather than using Kafka consumer offsets. For
> example, an HDFS connector might record offsets in HDFS to provide exactly
> once delivery. When the SinkTask is started or a rebalance occurs, the task
> would reload offsets from HDFS. In this case, disabling consumer offset
> commit will save some CPU cycles and network IOs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)