|
1 | 1 | [[runtime]]
|
2 | 2 | == Runtime fields
|
3 |
| -beta::[] |
4 | 3 | A _runtime field_ is a field that is evaluated at query time. Runtime fields
|
5 | 4 | enable you to:
|
6 | 5 |
|
@@ -71,7 +70,6 @@ against runtime fields.
|
71 | 70 |
|
72 | 71 | [[runtime-mapping-fields]]
|
73 | 72 | === Map a runtime field
|
74 |
| -beta::[] |
75 | 73 | You map runtime fields by adding a `runtime` section under the mapping
|
76 | 74 | definition and defining
|
77 | 75 | <<modules-scripting-using,a Painless script>>. This script has access to the
|
@@ -199,7 +197,6 @@ to `boolean`, or if the runtime field is removed.
|
199 | 197 |
|
200 | 198 | [[runtime-search-request]]
|
201 | 199 | === Define runtime fields in a search request
|
202 |
| -beta::[] |
203 | 200 | You can specify a `runtime_mappings` section in a search request to create
|
204 | 201 | runtime fields that exist only as part of the query. You specify a script
|
205 | 202 | as part of the `runtime_mappings` section, just as you would if adding a
|
@@ -246,7 +243,6 @@ section of the index mapping.
|
246 | 243 |
|
247 | 244 | [[runtime-override-values]]
|
248 | 245 | === Override field values at query time
|
249 |
| -beta::[] |
250 | 246 | If you create a runtime field with the same name as a field that
|
251 | 247 | already exists in the mapping, the runtime field shadows the mapped field. At
|
252 | 248 | query time, {es} evaluates the runtime field, calculates a value based on the
|
@@ -441,7 +437,6 @@ which still returns in the response:
|
441 | 437 |
|
442 | 438 | [[runtime-retrieving-fields]]
|
443 | 439 | === Retrieve a runtime field
|
444 |
| -beta::[] |
445 | 440 | Use the <<search-fields,`fields`>> parameter on the `_search` API to retrieve
|
446 | 441 | the values of runtime fields. Runtime fields won't display in `_source`, but
|
447 | 442 | the `fields` API works for all fields, even those that were not sent as part of
|
@@ -622,7 +617,6 @@ address.
|
622 | 617 |
|
623 | 618 | [[runtime-examples]]
|
624 | 619 | === Explore your data with runtime fields
|
625 |
| -beta::[] |
626 | 620 | Consider a large set of log data that you want to extract fields from.
|
627 | 621 | Indexing the data is time consuming and uses a lot of disk space, and you just
|
628 | 622 | want to explore the data structure without committing to a schema up front.
|
|
0 commit comments