feat(elasticsearch): add retry_on_conflict option on output #3147
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This introduces the
RetryOnConflict
option to the Elasticsearch output configuration. This option allows users to specify the number of times an update or upsert should be retried in the case of a version conflict.This feature is useful for scenarios where multiple clients might be updating the same document concurrently, and version conflicts are expected.
Change(s)
RetryOnConflict
field to the Elasticsearch output configuration.Testing
Issue(s)