From d57744e5b00df50918b2ce3f129361eedd67159f Mon Sep 17 00:00:00 2001 From: elasticsearchmachine <58790826+elasticsearchmachine@users.noreply.github.com> Date: Wed, 4 Aug 2021 11:48:50 -0400 Subject: [PATCH] [DOCS] Add retrieving runtime fields to introduction (#76084) (#76101) Co-authored-by: Adam Locke --- docs/reference/mapping/runtime.asciidoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/reference/mapping/runtime.asciidoc b/docs/reference/mapping/runtime.asciidoc index c8140e1e59991..eafc18eb2cf87 100644 --- a/docs/reference/mapping/runtime.asciidoc +++ b/docs/reference/mapping/runtime.asciidoc @@ -14,6 +14,11 @@ sees runtime fields no differently. You can define runtime fields in the <>. Your choice, which is part of the inherent flexibility of runtime fields. +Use the <> parameter on the `_search` API to +<>. Runtime +fields won't display in `_source`, but the `fields` API works for all fields, +even those that were not sent as part of the original `_source`. + Runtime fields are useful when working with log data (see <>), especially when you're unsure about the data structure. Your search speed decreases, but your index size is much @@ -632,6 +637,7 @@ which still returns in the response: [[runtime-retrieving-fields]] === Retrieve a runtime field + Use the <> parameter on the `_search` API to retrieve the values of runtime fields. Runtime fields won't display in `_source`, but the `fields` API works for all fields, even those that were not sent as part of