[
https://issues.apache.org/jira/browse/FLINK-38371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-38371:
-----------------------------------
Labels: pull-request-available (was: )
> Add `sink.retry-on-conflicts` option to Elasticsearch Sink
> ----------------------------------------------------------
>
> Key: FLINK-38371
> URL: https://issues.apache.org/jira/browse/FLINK-38371
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / ElasticSearch
> Reporter: Liu
> Priority: Major
> Labels: pull-request-available
>
> This Jira intends to introduces a new configuration option,
> sink.retry-on-conflicts, for the Elasticsearch table sink. This option allows
> users to specify the number of times to retry an update request when a
> version conflict or other cases occur.
> In high-throughput streaming scenarios, it's possible for concurrent updates
> to the same document ID to cause version conflicts in Elasticsearch, leading
> to data loss. By setting this option, the sink can automatically retry the
> failed update, making the connector more resilient to such conflicts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
