[
https://issues.apache.org/jira/browse/FLINK-28595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-28595:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> KafkaSource should not read metadata of unmatched regex topics
> --------------------------------------------------------------
>
> Key: FLINK-28595
> URL: https://issues.apache.org/jira/browse/FLINK-28595
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> Reporter: Afzal Mazhar
> Assignee: JasonLee
> Priority: Minor
> Labels: pull-request-available, stale-assigned
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> When we use a regex to subscribe to topics, the current connector gets a list
> of all topics, then runs describe against all of them, and finally filters by
> the regex pattern. This is not performant, as well as could possibly trigger
> audit alarms against sensitive topics that do not match the regex.
> Proposed fix: move the regex filtering from the TopicPatternSubscriber's
> set() down into KafkaSubscriberUtils getAllTopicMetadata(). Get the list of
> topics, filter by pattern (if any), then get metadata. Create appropriate
> tests.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
