Skip to content

Commit 55ada03

Browse files
author
Adam Locke
authored
[DOCS] [7.x] Remove beta admonition for runtime fields. (#69562)
1 parent 4ad367c commit 55ada03

File tree

3 files changed

+0
-8
lines changed

3 files changed

+0
-8
lines changed

docs/painless/painless-contexts/painless-runtime-fields-context.asciidoc

-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
[[painless-runtime-fields-context]]
22
=== Runtime fields context
3-
beta::[]
43
Use a Painless script to calculate and emit
54
<<painless-runtime-fields,runtime field>> values.
65

docs/painless/painless-guide/painless-runtime-fields.asciidoc

-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
[[painless-runtime-fields]]
22
=== Use Painless scripts in runtime fields
3-
beta::[]
43
A runtime field is a field that is evaluated at query time. When you define a
54
runtime field, you can immediately use it in search requests, aggregations,
65
filtering, and sorting.

docs/reference/mapping/runtime.asciidoc

-6
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,5 @@
11
[[runtime]]
22
== Runtime fields
3-
beta::[]
43
A _runtime field_ is a field that is evaluated at query time. Runtime fields
54
enable you to:
65

@@ -71,7 +70,6 @@ against runtime fields.
7170

7271
[[runtime-mapping-fields]]
7372
=== Map a runtime field
74-
beta::[]
7573
You map runtime fields by adding a `runtime` section under the mapping
7674
definition and defining
7775
<<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.
199197

200198
[[runtime-search-request]]
201199
=== Define runtime fields in a search request
202-
beta::[]
203200
You can specify a `runtime_mappings` section in a search request to create
204201
runtime fields that exist only as part of the query. You specify a script
205202
as part of the `runtime_mappings` section, just as you would if adding a
@@ -246,7 +243,6 @@ section of the index mapping.
246243

247244
[[runtime-override-values]]
248245
=== Override field values at query time
249-
beta::[]
250246
If you create a runtime field with the same name as a field that
251247
already exists in the mapping, the runtime field shadows the mapped field. At
252248
query time, {es} evaluates the runtime field, calculates a value based on the
@@ -441,7 +437,6 @@ which still returns in the response:
441437

442438
[[runtime-retrieving-fields]]
443439
=== Retrieve a runtime field
444-
beta::[]
445440
Use the <<search-fields,`fields`>> parameter on the `_search` API to retrieve
446441
the values of runtime fields. Runtime fields won't display in `_source`, but
447442
the `fields` API works for all fields, even those that were not sent as part of
@@ -622,7 +617,6 @@ address.
622617

623618
[[runtime-examples]]
624619
=== Explore your data with runtime fields
625-
beta::[]
626620
Consider a large set of log data that you want to extract fields from.
627621
Indexing the data is time consuming and uses a lot of disk space, and you just
628622
want to explore the data structure without committing to a schema up front.

0 commit comments

Comments
 (0)