From 04f19bbaa41cd1f694455f0955cbb49460914466 Mon Sep 17 00:00:00 2001 From: Colin Goodheart-Smithe Date: Mon, 16 Jan 2017 09:13:21 +0000 Subject: [PATCH] [DOCS]cMake it clear that bulk API actions are processed sequentially on each shard rather than sequentially overall (#22550) --- docs/reference/getting-started.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/getting-started.asciidoc b/docs/reference/getting-started.asciidoc index 0f285ecb13b..8827e519b1f 100755 --- a/docs/reference/getting-started.asciidoc +++ b/docs/reference/getting-started.asciidoc @@ -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. -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