Skip to content

[DOCS] [7.x] Remove beta admonition for runtime fields. #69562

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
[[painless-runtime-fields-context]]
=== Runtime fields context
beta::[]
Use a Painless script to calculate and emit
<<painless-runtime-fields,runtime field>> values.

Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
[[painless-runtime-fields]]
=== Use Painless scripts in runtime fields
beta::[]
A runtime field is a field that is evaluated at query time. When you define a
runtime field, you can immediately use it in search requests, aggregations,
filtering, and sorting.
Expand Down
6 changes: 0 additions & 6 deletions docs/reference/mapping/runtime.asciidoc
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
[[runtime]]
== Runtime fields
beta::[]
A _runtime field_ is a field that is evaluated at query time. Runtime fields
enable you to:

Expand Down Expand Up @@ -71,7 +70,6 @@ against runtime fields.

[[runtime-mapping-fields]]
=== Map a runtime field
beta::[]
You map runtime fields by adding a `runtime` section under the mapping
definition and defining
<<modules-scripting-using,a Painless script>>. This script has access to the
Expand Down Expand Up @@ -199,7 +197,6 @@ to `boolean`, or if the runtime field is removed.

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

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

[[runtime-retrieving-fields]]
=== Retrieve a runtime field
beta::[]
Use the <<search-fields,`fields`>> 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
Expand Down Expand Up @@ -622,7 +617,6 @@ address.

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