[
https://issues.apache.org/jira/browse/KAFKA-15538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17831034#comment-17831034
]
Kirk True commented on KAFKA-15538:
-----------------------------------
[~phuctran]—The {{ConsumerCoordinator}} has code to [update the set of topics
when the metadata is
updated|https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java#L435].
I don't see that we have the analogue for that in the new consumer :(
[~lianetm]/[~pnee]—do you know if/where we update the set of topics for
pattern-based subscriptions apart from the initial {{subscribe(Pattern)}} call?
> Client support for java regex based subscription
> ------------------------------------------------
>
> Key: KAFKA-15538
> URL: https://issues.apache.org/jira/browse/KAFKA-15538
> Project: Kafka
> Issue Type: Sub-task
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Phuc Hong Tran
> Priority: Blocker
> Labels: kip-848-client-support, newbie, regex
> Fix For: 3.8.0
>
>
> When using subscribe with a java regex (Pattern), we need to resolve it on
> the client side to send the broker a list of topic names to subscribe to.
> Context:
> The new consumer group protocol uses [Google
> RE2/J|https://github.com/google/re2j] for regular expressions and introduces
> new methods in the consumer API to subscribe using a `SubscribePattern`. The
> subscribe using a java `Pattern` will be still supported for a while but
> eventually removed.
> * When the subscribe with SubscriptionPattern is used, the client should
> just send the regex to the broker and it will be resolved on the server side.
> * In the case of the subscribe with Pattern, the regex should be resolved on
> the client side.
> As part of this task, we should re-enable all integration tests defined in
> the PlainTextAsyncConsumer that relate to subscription with pattern and that
> are currently disabled for the new consumer + new protocol
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
