You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (JIRA)" <ji...@apache.org> on 2019/02/28 11:21:00 UTC
[jira] [Closed] (FLINK-10342) Kafka duplicate topic consumption
when topic name is changed
[ https://issues.apache.org/jira/browse/FLINK-10342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tzu-Li (Gordon) Tai closed FLINK-10342.
---------------------------------------
Resolution: Fixed
Release Note: Starting from 1.8.0, the {{FlinkKafkaConsumer}} now always filter out restored partitions that are no longer associated with a specified topic to subscribe to in the restored execution. This behaviour did not exist in previous versions of the {{FlinkKafkaConsumer}}. If you wish to retain the previous behaviour, please use the {{disableFilterRestoredPartitionsWithSubscribedTopics}} configuration method on the {{FlinkKafkaConsumer}}.
Thanks for the contribution [~f.li]!
Merged:
1.8.0 - 572a57c62e6d78b371605e3731e48a1dd18d38d4
1.9.0 - 6a4f0124512a424510f1dcdbe7855c92617e78c6
> Kafka duplicate topic consumption when topic name is changed
> ------------------------------------------------------------
>
> Key: FLINK-10342
> URL: https://issues.apache.org/jira/browse/FLINK-10342
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
> Reporter: Oleksandr Nitavskyi
> Assignee: Feng LI
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In case of topic name is simply renamed for a KafkaConsumer Flink starts to consume from old and a new topic in the same time which can lead to unexpected behavior.
> Here is the PR with reproduce: https://github.com/apache/flink/pull/6691
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)