[
https://issues.apache.org/jira/browse/FLINK-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-3037:
----------------------------------
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.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
