[jira] [Updated] (FLINK-35228) DynamicKafkaSource does not read re-added topic for the same cluster
[ https://issues.apache.org/jira/browse/FLINK-35228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mason Chen updated FLINK-35228: --- Fix Version/s: kafka-3.3.0 > DynamicKafkaSource does not read re-added topic for the same cluster > > > Key: FLINK-35228 > URL: https://issues.apache.org/jira/browse/FLINK-35228 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: kafka-3.1.0 >Reporter: Ignas Daukšas >Assignee: Ignas Daukšas >Priority: Major > Labels: pull-request-available > Fix For: kafka-3.3.0 > > > When using DynamicKafkaSource, if topic is removed from the cluster (that has > more active topics remaining) and then re-added back, consumption from that > topic won't be happening. > However, if the topic in question is the only topic in that cluster, then > everything works as expected - consumption restarts once cluster-topic is > re-added. > Steps to reproduce: > # Have a DynamicKafkaSource. > # Have KafkaMetadataService report a single cluster with two topics (A and > B) for the subscribed stream/streams. > # Consume some data, topics A and B are consumed as expected. > # Have KafkaMetadataService remove topic A. > # Continue consuming data, only topic B consumed as expected. > # Have KafkaMetadataService re-add topic A. > # Continue consuming data, however only topic B is actually consumed - this > is not expected. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35228) DynamicKafkaSource does not read re-added topic for the same cluster
[ https://issues.apache.org/jira/browse/FLINK-35228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-35228: --- Labels: pull-request-available (was: ) > DynamicKafkaSource does not read re-added topic for the same cluster > > > Key: FLINK-35228 > URL: https://issues.apache.org/jira/browse/FLINK-35228 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: kafka-3.1.0 >Reporter: Ignas Daukšas >Priority: Major > Labels: pull-request-available > > When using DynamicKafkaSource, if topic is removed from the cluster (that has > more active topics remaining) and then re-added back, consumption from that > topic won't be happening. > However, if the topic in question is the only topic in that cluster, then > everything works as expected - consumption restarts once cluster-topic is > re-added. > Steps to reproduce: > # Have a DynamicKafkaSource. > # Have KafkaMetadataService report a single cluster with two topics (A and > B) for the subscribed stream/streams. > # Consume some data, topics A and B are consumed as expected. > # Have KafkaMetadataService remove topic A. > # Continue consuming data, only topic B consumed as expected. > # Have KafkaMetadataService re-add topic A. > # Continue consuming data, however only topic B is actually consumed - this > is not expected. -- This message was sent by Atlassian Jira (v8.20.10#820010)
