You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dawid Wysakowicz (JIRA)" <ji...@apache.org> on 2019/02/25 12:34:01 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16776823#comment-16776823 ]
Dawid Wysakowicz commented on FLINK-10342:
------------------------------------------
I think in respect to the consensus in this thread: https://lists.apache.org/thread.html/7e2a2b6fb40c4d1cd83b1e4bd63ad8ebbbc26e2d5c74b1d6fd44cdee@%3Cdev.flink.apache.org%3E we should reopen this issue.
> 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
> Reporter: Oleksandr Nitavskyi
> Assignee: Oleksandr Nitavskyi
> Priority: Minor
>
> 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)