[
https://issues.apache.org/jira/browse/KAFKA-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276663#comment-15276663
]
Jiangjie Qin commented on KAFKA-3664:
-------------------------------------
[~hachikuji] That sounds reasonable. That is a what I am currently doing as a
workaround, i.e. committing the offset manually before unsubscribe. As long as
we document it clearly it should be fine.
> When subscription set changes on new consumer, the partitions may be removed
> without offset being committed.
> ------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-3664
> URL: https://issues.apache.org/jira/browse/KAFKA-3664
> Project: Kafka
> Issue Type: Bug
> Reporter: Jiangjie Qin
> Assignee: Vahid Hashemian
>
> When users are using group management, if they call consumer.subscribe() to
> change the subscription, the removed subscriptions will be immediately
> removed and their offset will not be commit. Also the revoked partitions
> passed to the ConsumerRebalanceListener.onPartitionsRevoked() will not
> include those partitions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
