You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Shikhar Bhushan (JIRA)" <ji...@apache.org> on 2016/11/15 00:24:58 UTC

[jira] [Updated] (KAFKA-3462) Allow SinkTasks to disable consumer offset commit

     [ https://issues.apache.org/jira/browse/KAFKA-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shikhar Bhushan updated KAFKA-3462:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

This will be handled with KIP-89 / KAFKA-4161. Tasks that wish to disable framework-managed offset commits can return an empty map from {{SinkTask.preCommit()}} to make it a no-op.

> Allow SinkTasks to disable consumer offset commit 
> --------------------------------------------------
>
>                 Key: KAFKA-3462
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3462
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions: 0.10.1.0
>            Reporter: Liquan Pei
>            Assignee: Liquan Pei
>            Priority: Minor
>             Fix For: 0.10.2.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)