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

Arvid Heise resolved FLINK-36210.
---------------------------------
    Fix Version/s: kafka-3.3.0
       Resolution: Fixed

Merged into main as 
https://github.com/apache/flink-connector-kafka/commit/7929b16dcfe648da30b6cc9755f63de2ed3d5319

> Optimize the logic for fetching topic metadata in the TopicPatternSubscriber 
> mode
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-36210
>                 URL: https://issues.apache.org/jira/browse/FLINK-36210
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kafka
>            Reporter: xiaochen.zhou
>            Assignee: xiaochen.zhou
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: kafka-3.3.0
>
>
> In {{TopicPatternSubscriber}} mode, our current logic for fetch topic 
> metadata for all topics and then filtering it. We can optimize this by first 
> filtering the topic names and then fetch metadata only for the filtered 
> topics to speed up task recovery.



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

Reply via email to