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

Document removal of forced versioning for update API (#28834)

This commit is contained in:
Bojan Matić 2018-02-28 18:38:44 +01:00 committed by Boaz Leskes
parent 95dea2408d
commit 742e9f5078
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/reference/docs/update.asciidoc
View File

@ -307,22 +307,20 @@ By default the updated source is not returned.
See <<search-request-source-filtering, `source filtering`>> 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
<<docs-index_,`index` API>> instead.
=====================================================