[
https://issues.apache.org/jira/browse/FLINK-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328965#comment-17328965
]
Flink Jira Bot commented on FLINK-3037:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Make the behavior of the Kafka consumer configurable if the offsets to
> restore from are not available
> -----------------------------------------------------------------------------------------------------
>
> Key: FLINK-3037
> URL: https://issues.apache.org/jira/browse/FLINK-3037
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> Reporter: Robert Metzger
> Priority: Major
> Labels: stale-major
>
> Currently, if the {{FlinkKafkaConsumer}} is restoring a checkpoint and the
> offset is not available anymore in Kafka, its restoring according to
> {{auto.offset.reset}}.
> This leads to inconsistent behavior (not exactly-once anymore) because the
> operators will not receive data in sync with the checkpoint.
> With this pull request, I would like to make the behavior controllable, using
> a flag. The simplest approach would be to let the consumer fail in that case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
