[
https://issues.apache.org/jira/browse/KAFKA-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15536297#comment-15536297
]
Vahid Hashemian commented on KAFKA-4234:
----------------------------------------
Sounds fair. One approach would be to somehow preserve the offset(s) before the
last {{poll}} so that if issues occurred after the {{poll}} we are able to
reset (or {{rewind}} as suggested in the other thread) without having to
perform an {{unsubscribe}}. But as you suggested, we can think more about this
during the next release cycle. I'll start working on this today.
> Consumer should not commit offsets in unsubscribe()
> ---------------------------------------------------
>
> Key: KAFKA-4234
> URL: https://issues.apache.org/jira/browse/KAFKA-4234
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Reporter: Jason Gustafson
> Assignee: Vahid Hashemian
> Fix For: 0.10.1.0
>
>
> In KIP-70, we changed the behavior of {{unsubscribe}} to commit offsets if
> autocommit is enabled. Unfortunately, because of the issue documented in
> KAFKA-3491, this makes it impossible to abort processing if an exception is
> thrown while processing some records. Until we have a fix for this problem,
> we should probably revert this behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
