[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
