From 742e9f507817ef25d7857f24c623dd307c640079 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bojan=20Mati=C4=87?= Date: Wed, 28 Feb 2018 18:38:44 +0100 Subject: [PATCH] Document removal of forced versioning for update API (#28834) --- docs/reference/docs/update.asciidoc | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/docs/reference/docs/update.asciidoc b/docs/reference/docs/update.asciidoc index 6a0f09c982b..18aee6094f8 100644 --- a/docs/reference/docs/update.asciidoc +++ b/docs/reference/docs/update.asciidoc @@ -307,22 +307,20 @@ By default the updated source is not returned. See <> for details. -`version` & `version_type`:: +`version`:: The update API uses the Elasticsearch's versioning support internally to make sure the document doesn't change during the update. You can use the `version` parameter to specify that the document should only be updated if its version -matches the one specified. By setting version type to `force` you can force -the new version of the document after update (use with care! with `force` -there is no guarantee the document didn't change). +matches the one specified. [NOTE] -.The update API does not support external versioning +.The update API does not support versioning other than internal ===================================================== -External versioning (version types `external` & `external_gte`) is not -supported by the update API as it would result in Elasticsearch version -numbers being out of sync with the external system. Use the +External (version types `external` & `external_gte`) or forced (version type `force`) +versioning is not supported by the update API as it would result in Elasticsearch +version numbers being out of sync with the external system. Use the <> instead. =====================================================