[
https://issues.apache.org/jira/browse/KAFKA-20119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18057729#comment-18057729
]
Chia-Ping Tsai commented on KAFKA-20119:
----------------------------------------
I've opened KAFKA-20166 to correct the behavior, so let's focus on the docs
updates in this ticket
> Clarify that `Consumer#unsubscribe` does not trigger auto-commit
> ----------------------------------------------------------------
>
> Key: KAFKA-20119
> URL: https://issues.apache.org/jira/browse/KAFKA-20119
> Project: Kafka
> Issue Type: Improvement
> Components: clients, consumer, docs
> Reporter: Chia-Ping Tsai
> Assignee: TaiJuWu
> Priority: Minor
>
> I suggest adding a note to clarify that unsubscribe() does not guarantee a
> commit, which could lead to duplicate processing if offsets are not manually
> committed.
> {code:java}
> Note: Unlike close(), this method does not guarantee that pending offsets are
> committed before unsubscribing, even if enable.auto.commit is enabled. To
> avoid duplicate processing upon re-joining, it is recommended to explicitly
> call {@link #commitSync()} before invoking this method
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
