[
https://issues.apache.org/jira/browse/KAFKA-18729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923773#comment-17923773
]
Lianet Magrans commented on KAFKA-18729:
----------------------------------------
[~m1a2st] more context:
Initial PR discussion here
[https://github.com/apache/kafka/pull/18777#discussion_r1941488787]
Good to tackle this one with https://issues.apache.org/jira/browse/KAFKA-18117
in mind, just to be on the same page about moving towards topicIds (instead of
topicNames) whenever possible. I'll start working on 18117 soon (right after
wrapping up 4.0)
> Improve consumer check for assigned topics from regex
> -----------------------------------------------------
>
> Key: KAFKA-18729
> URL: https://issues.apache.org/jira/browse/KAFKA-18729
> Project: Kafka
> Issue Type: Improvement
> Components: consumer
> Reporter: Lianet Magrans
> Assignee: 黃竣陽
> Priority: Major
> Fix For: 4.1.0
>
>
> When using subscriptions to broker-side regex RE2J, the consumer checks if a
> topic received in metadata is assigned in order to keep its info. At the
> moment, the consumer has no other way but to check the topic against the list
> of assigned topicPartitions (which is all that's available).
> We should consider improving the check to do it at the topic level, not
> topicPartition level . We would need to keep the set of assigned topics from
> RE2J regex in the subscription state, updated as assignments as reconciled
> and partitions are add/removed. Then we could rely on this topic set for the
> check (not all the assigned topicPartitions set)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
