[docs] Deprecate found and created (#19633)

These parts of delete and index response have been replaced with the
operation field.
This commit is contained in:
Nik Everett 2016-07-28 10:20:48 -04:00 committed by GitHub
parent 4d1cc5296c
commit f159156931
1 changed files with 14 additions and 0 deletions

View File

@ -11,6 +11,20 @@ url entirely. If you add `?refresh=wait_for` Elasticsearch will wait for the
changes to become visible before replying to the request but won't take any changes to become visible before replying to the request but won't take any
immediate refresh related action. See <<docs-refresh>>. immediate refresh related action. See <<docs-refresh>>.
==== `created` field deprecated in the Index API
The `created` field has been deprecated in the Index API. It now returns
`operation`, returning `"operation": "create"` when it created a document and
`"operation": "index"` when it updated the document. This is also true for
`index` bulk operations.
==== `found` field deprecated in the Delete API
The `found` field has been deprecated in the Delete API. It now returns
`operation`, returning `"operation": "deleted"` when it deleted a document and
`"operation": "noop"` when it didn't found the document. This is also true for
`index` bulk operations.
==== Reindex and Update By Query ==== Reindex and Update By Query
Before 5.0.0 `_reindex` and `_update_by_query` only retried bulk failures so Before 5.0.0 `_reindex` and `_update_by_query` only retried bulk failures so
they used the following response format: they used the following response format: