[DOCS] Add deprecation message for scripted fields (#95964)
* [DOCS] Add deprecation message for scripted fields * Change deprecation to full block admonition.
This commit is contained in:
parent
0fce2427e5
commit
3eb0996920
|
@ -78,6 +78,7 @@ include::field-formatters/color-formatter.asciidoc[]
|
|||
|
||||
[[scripted-fields]]
|
||||
=== Scripted fields
|
||||
deprecated::[7.13,Use {ref}/runtime.html[runtime fields] instead of scripted fields. Runtime fields support Painless scripts and provide greater flexibility.]
|
||||
|
||||
Scripted fields compute data on the fly from the data in your {es} indices. The data is shown on
|
||||
the Discover tab as part of the document data, and you can use scripted fields in your visualizations. You query scripted fields with the <<kuery-query, {kib} query language>>, and can filter them using the filter bar. The scripted field values are computed at query time, so they aren't indexed and cannot be searched using the {kib} default
|
||||
|
@ -87,7 +88,7 @@ WARNING: Computing data on the fly with scripted fields can be very resource int
|
|||
{kib} performance. Keep in mind that there's no built-in validation of a scripted field. If your scripts are
|
||||
buggy, you'll get exceptions whenever you try to view the dynamically generated data.
|
||||
|
||||
When you define a scripted field in {kib}, you have a choice of the {ref}/modules-scripting-expression.html[Lucene expressions] or the
|
||||
When you define a scripted field in {kib}, you have a choice of the {ref}/modules-scripting-expression.html[Lucene expressions] or the
|
||||
{ref}/modules-scripting-painless.html[Painless] scripting language.
|
||||
|
||||
You can reference any single value numeric field in your expressions, for example:
|
||||
|
|
Loading…
Reference in a new issue