Skip to content

Commit

Permalink
Reindex conflicts clarification (docs) (elastic#40442)
Browse files Browse the repository at this point in the history
Made it more clear that conflicts : proceed only affects version
conflicts.
  • Loading branch information
henningandersen authored Mar 29, 2019
1 parent c9d05ad commit e24fd1b
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions docs/reference/docs/reindex.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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]
--------------------------------------------------
Expand Down

0 comments on commit e24fd1b

Please sign in to comment.