[ https://issues.apache.org/jira/browse/FLINK-31648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-31648: ----------------------------------- Labels: pull-request-available stale-assigned (was: pull-request-available) I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issue is assigned but has not received an update in 30 days, so it has been labeled "stale-assigned". If you are still working on the issue, please remove the label and add a comment updating the community on your progress. If this issue is waiting on feedback, please consider this a reminder to the committer/reviewer. Flink is a very active project, and so we appreciate your patience. If you are no longer working on the issue, please unassign yourself so someone else may work on it. > Elasticsearch supports retrying writes when concurrency issues occur > -------------------------------------------------------------------- > > Key: FLINK-31648 > URL: https://issues.apache.org/jira/browse/FLINK-31648 > Project: Flink > Issue Type: New Feature > Components: Connectors / ElasticSearch > Affects Versions: 1.14.6 > Reporter: 陈磊 > Assignee: 陈磊 > Priority: Major > Labels: pull-request-available, stale-assigned > > Elasticsearch supports retrying writes when concurrency issues occur.The > exception information is as follows: > ElasticsearchException[Elasticsearch exception > [type=version_conflict_engine_exception, reason=[******][******]: version > conflict, current version [2] is different than the one provided [1]]]] -- This message was sent by Atlassian Jira (v8.20.10#820010)