honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify the order of responses to a bulk request (#36441) 

Bulk requests comprise many individual actions, and the responses for each
action comes back in the same order (see e.g. `DocumentActionsIT#testBulk()`).
However the docs do not seem to explicitly state this vital fact. This commit
addresses that omission.
This commit is contained in:
David Turner 2018-12-11 09:02:23 +00:00 committed by GitHub
parent 2bf0583fec
commit bf42cedc13
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/reference/docs/bulk.asciidoc
View File

@ -185,9 +185,10 @@ Client libraries using this protocol should try and strive to do
something similar on the client side, and reduce buffering as much as
possible.
The response to a bulk action is a large JSON structure with the
individual results of each action that was performed. The failure of a
single action does not affect the remaining actions.
The response to a bulk action is a large JSON structure with the individual
results of each action that was performed in the same order as the actions that
appeared in the request. The failure of a single action does not affect the
remaining actions.
There is no "correct" number of actions to perform in a single bulk
call. You should experiment with different settings to find the optimum