From 4bdc1be5a572e04746d0c0cf8d7883daf033b4b9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christoph=20B=C3=BCscher?= Date: Wed, 10 Feb 2021 11:27:20 +0100 Subject: [PATCH] Add note about changed `fields` API behaviour for `nested` Add a note about the changes in the `fields` API around the response format for nested fields. Relates to #67432 --- docs/reference/migration/migrate_7_12.asciidoc | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/reference/migration/migrate_7_12.asciidoc b/docs/reference/migration/migrate_7_12.asciidoc index 7ec6c8a88035a..4aed4c0d71aa7 100644 --- a/docs/reference/migration/migrate_7_12.asciidoc +++ b/docs/reference/migration/migrate_7_12.asciidoc @@ -48,6 +48,21 @@ force-merge on these immutable indices will fail if the requested merge is not a no-op. ==== +[discrete] +[[breaking_712_search_changes]] +==== Search changes + +[[fields-api-nested-fields]] +.The search APIs `fields` parameter returns fields inside `nested` fields grouped together. +[%collapsible] +==== +*Details* + +In earlier versions, fields retrieved via `fields` in the search API were +returned as a flat list. From 7.12 on, fields inside an object that is mapped +using the `nested` field type are grouped together to maintain the independence of +each object inside the original nested array. +==== + //// [discrete] [[deprecated-7.11]]