[
https://issues.apache.org/jira/browse/KAFKA-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15534782#comment-15534782
]
Jason Gustafson commented on KAFKA-4234:
----------------------------------------
Yeah, since there's no consensus how to address the problem at the moment, I
think it would make sense to let the current workaround of calling
unsubscribe() continue to work as it has in previous releases. Otherwise users
have no way to abort if an exception occurs, which kind of limits the
usefulness of autocommit. In the next release cycle, we can come up with a
better solution for this problem and then decide whether {{unsubscribe()}}
should send an offset commit or not. What do you think?
> 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
> 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)
