[ 
https://issues.apache.org/jira/browse/KAFKA-18117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lianet Magrans updated KAFKA-18117:
-----------------------------------
    Description: 
Include support for topicIds in subscription state to properly align with the 
new protocol assignments that contain topic IDs only (no name). This will allow 
the consumer to request metadata for assigned topic IDs only (not all topics). 

Note that without this (current state), the consumer requests metadata for all 
topic IDs when subscribed to the new RE2J regex (because the SubscriptionState 
doesn't know about topic IDs, only topic names). The assigned topic IDs live 
only within the MembershipMgr that handled the assignment)

  was:Include support for topicIds in subscription state to properly align with 
the new protocol assignments that contain topic IDs only (no name). This will 
allow the consumer to request metadata for assigned topic IDs only (not all 
topics). 


> Support topic IDs in consumer SubscriptionState
> -----------------------------------------------
>
>                 Key: KAFKA-18117
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18117
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, consumer
>            Reporter: Lianet Magrans
>            Assignee: Lianet Magrans
>            Priority: Major
>              Labels: kip-848-client-support
>             Fix For: 4.1.0
>
>
> Include support for topicIds in subscription state to properly align with the 
> new protocol assignments that contain topic IDs only (no name). This will 
> allow the consumer to request metadata for assigned topic IDs only (not all 
> topics). 
> Note that without this (current state), the consumer requests metadata for 
> all topic IDs when subscribed to the new RE2J regex (because the 
> SubscriptionState doesn't know about topic IDs, only topic names). The 
> assigned topic IDs live only within the MembershipMgr that handled the 
> assignment)



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

Reply via email to