Reindex conflicts clarification (docs) (#40442)

Made it more clear that conflicts : proceed only affects version
conflicts.
This commit is contained in:
Henning Andersen 2019-03-30 00:43:15 +01:00 committed by Henning Andersen
parent 1b95ddfa3b
commit 567e8f8b63
1 changed files with 5 additions and 2 deletions

View File

@ -118,8 +118,11 @@ POST _reindex
// CONSOLE
// TEST[setup:twitter]
By default, version conflicts abort the `_reindex` process, but you can just
count them by setting `"conflicts": "proceed"` in the request body:
By default, version conflicts abort the `_reindex` process. The `"conflicts"` request body
parameter can be used to instruct `_reindex` to proceed with the next document on version conflicts.
It is important to note that the handling of other error types is unaffected by the `"conflicts"` parameter.
When `"conflicts": "proceed"` is set in the request body, the `_reindex` process will continue on version conflicts
and return a count of version conflicts encountered:
[source,js]
--------------------------------------------------