[
https://issues.apache.org/jira/browse/FLINK-10806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891724#comment-16891724
]
Jiangjie Qin commented on FLINK-10806:
--------------------------------------
[~wind_ljy] I think it might still worth having either earliest/latest support,
because they are supported by KafkaConsumer. So providing them would let users
have the same experience as KafkaConsumer. We may need to consider the
backwards compatibility in this case. We may have to introduce a new config in
order to ensure backwards compatibility. Doing that may require a FLIP. I can
include that in the FLIP for FLINK-11654. What do you think?
> 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: Connectors / Kafka
> Affects Versions: 1.6.2, 1.8.1
> 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.14#76016)
