From f1591569319a2824ee3f428ad1cdc491c100c9c8 Mon Sep 17 00:00:00 2001 From: Nik Everett Date: Thu, 28 Jul 2016 10:20:48 -0400 Subject: [PATCH] [docs] Deprecate found and created (#19633) These parts of delete and index response have been replaced with the operation field. --- docs/reference/migration/migrate_5_0/docs.asciidoc | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/reference/migration/migrate_5_0/docs.asciidoc b/docs/reference/migration/migrate_5_0/docs.asciidoc index 9149eed6142..104f047056d 100644 --- a/docs/reference/migration/migrate_5_0/docs.asciidoc +++ b/docs/reference/migration/migrate_5_0/docs.asciidoc @@ -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 immediate refresh related action. See <>. +==== `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 Before 5.0.0 `_reindex` and `_update_by_query` only retried bulk failures so they used the following response format: