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

[DOCS]cMake it clear that bulk API actions are processed sequentially on each shard rather than sequentially overall (#22550)

This commit is contained in:
Colin Goodheart-Smithe 2017-01-16 09:13:21 +00:00
parent f6ee6e420b
commit 04f19bbaa4
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/reference/getting-started.asciidoc
View File

@ -551,7 +551,7 @@ POST /customer/external/_bulk?pretty
Note above that for the delete action, there is no corresponding source document after it since deletes only require the ID of the document to be deleted. Note above that for the delete action, there is no corresponding source document after it since deletes only require the ID of the document to be deleted.
The bulk API executes all the actions sequentially and in order. If a single action fails for whatever reason, it will continue to process the remainder of the actions after it. When the bulk API returns, it will provide a status for each action (in the same order it was sent in) so that you can check if a specific action failed or not. The Bulk API does not fail due to failures of in one of the actions. If a single action fails for whatever reason, it will continue to process the remainder of the actions after it. When the bulk API returns, it will provide a status for each action (in the same order it was sent in) so that you can check if a specific action failed or not.
== Exploring Your Data == Exploring Your Data