[jira] [Updated] (FLINK-3037) Make the behavior of the Kafka consumer configurable if the offsets to restore from are not available
[
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)
[jira] [Updated] (FLINK-3037) Make the behavior of the Kafka consumer configurable if the offsets to restore from are not available
[
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 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.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
[jira] [Updated] (FLINK-3037) Make the behavior of the Kafka consumer configurable if the offsets to restore from are not available
[
https://issues.apache.org/jira/browse/FLINK-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-3037:
--
Priority: Minor (was: Major)
> 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: Minor
> Labels: auto-deprioritized-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)
[jira] [Updated] (FLINK-3037) Make the behavior of the Kafka consumer configurable if the offsets to restore from are not available
[
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 (was: stale-major)
> 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: auto-deprioritized-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)
[jira] [Updated] (FLINK-3037) Make the behavior of the Kafka consumer configurable if the offsets to restore from are not available
[
https://issues.apache.org/jira/browse/FLINK-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-3037:
--
Labels: stale-major (was: )
> 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)
[jira] [Updated] (FLINK-3037) Make the behavior of the Kafka consumer configurable if the offsets to restore from are not available
[
https://issues.apache.org/jira/browse/FLINK-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger updated FLINK-3037:
--
Description:
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.
was:
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.
> 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: Kafka Connector
>Reporter: Robert Metzger
>
> 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
(v6.3.4#6332)
