You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Jiayi Liao (JIRA)" <ji...@apache.org> on 2018/11/07 03:45:00 UTC

[jira] [Updated] (FLINK-10806) Support multiple consuming offsets when discovering a new topic

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

Jiayi Liao updated FLINK-10806:
-------------------------------
    Summary: Support multiple consuming offsets when discovering a new topic  (was: Add optional consuming parameters when discovering a new topic)

> Support multiple consuming offsets when discovering a new topic
> ---------------------------------------------------------------
>
>                 Key: FLINK-10806
>                 URL: https://issues.apache.org/jira/browse/FLINK-10806
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kafka Connector
>    Affects Versions: 1.6.2
>            Reporter: Jiayi Liao
>            Assignee: Jiayi Liao
>            Priority: Major
>
> In KafkaConsumerBase, we discover the TopicPartitions and compare them with the restoredState. It's reasonable when a topic's partitions scaled. However, if we add a new topic which has too much data and restore the Flink program, the data of the new topic will be consumed from the start, which may not be what we want.  I think this should be an option for developers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)