You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "sanghyeok An (Jira)" <ji...@apache.org> on 2025/11/10 08:33:00 UTC

[jira] [Commented] (KAFKA-19393) Consolidate consumer assignment state views

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

sanghyeok An commented on KAFKA-19393:
--------------------------------------

Hi, [~lianetm] ! 

If you’re not currently working on this task, may I look into this issue?

> Consolidate consumer assignment state views
> -------------------------------------------
>
>                 Key: KAFKA-19393
>                 URL: https://issues.apache.org/jira/browse/KAFKA-19393
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients, consumer
>            Reporter: Lianet Magrans
>            Assignee: Lianet Magrans
>            Priority: Major
>              Labels: kip-848-client-support
>             Fix For: 4.2.0
>
>
> Currently the consumer assignment state is partly in the SubscriptionState (where group assignment is updated for both protocols), and in the ConsumerMembershipMgr (where assignment is initially received in HB responses and reconciled with the new Consumer protocol). 
> We should consider extracting the assignment state to have a single view of it, that could be used from the SubscriptionState and the MembershipMgrs.
> More context in PR comment (when dealing with making assigned topic IDs available in the SubscriptionState, as they are needed to request metadata for topics assigned when using broker-side regex) https://github.com/apache/kafka/pull/19814#discussion_r2131673167



--
This message was sent by Atlassian Jira
(v8.20.10#820010)