[
https://issues.apache.org/jira/browse/FLINK-21219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21219:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> FlinkKafkaConsumer ignores offset overrides for new topics when restoring
> from savepoint.
> -----------------------------------------------------------------------------------------
>
> Key: FLINK-21219
> URL: https://issues.apache.org/jira/browse/FLINK-21219
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
> Affects Versions: 1.12.1
> Reporter: Dominik Wosiński
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> Currently, when FlinkKafkaConsumer is restored from savepoint, the following
> code will handle topics that do not have offsets committed (for example if a
> new topic was added):
> {noformat}
> if (restoredState != null) { for (KafkaTopicPartition partition :
> allPartitions) { if (!restoredState.containsKey(partition)) {
> restoredState.put(partition,
> KafkaTopicPartitionStateSentinel.EARLIEST_OFFSET); } }{noformat}
>
> So if we have a KafkaConsumer with topicPattern and the pattern is changed,
> new topis will always start from earliest offset, even if originally the
> setting was different.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
