[jira] [Commented] (KAFKA-3664) When subscription set changes on new consumer, the partitions may be removed without offset being committed.

["Jason Gustafson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274390#comment-15274390 ] 

Jason Gustafson commented on KAFKA-3664:
----------------------------------------

[~becket_qin] Thanks for the report. After the topic subscription has been changed, do you think consumer.assignment() should continue to return partitions from any topics that were unsubscribed as well? That is, at least until we have rebalanced and gotten a new assignment? This would make the behavior of the revocation callback consistent if we decided to also include the unsubscribed partitions there. Do you think users would find this behavior surprising?

> 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)