maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Docs: Remove references to Goovy, JS and Py scripted fields (#82662)

Browse source
This commit is contained in:
Stuart Tettemer 2020-11-05 13:30:15 -06:00 committed by GitHub
parent 62443a6a05
commit eeebe580e3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/management/managing-fields.asciidoc
View file

@ -121,12 +121,8 @@ 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 {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. 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 scripting languages. In 5.0 and later, the default When you define a scripted field in {kib}, you have a choice of the {ref}/modules-scripting-expression.html[Lucene expressions] or the
options are {ref}/modules-scripting-expression.html[Lucene expressions] and {ref}/modules-scripting-painless.html[Painless]. {ref}/modules-scripting-painless.html[Painless] scripting language.
While you can use other scripting languages if you enable dynamic scripting for them in {es}, this is not recommended
because they cannot be sufficiently {ref}/modules-scripting-security.html[sandboxed].
WARNING: In 5.0 and later, Groovy, JavaScript, and Python scripting are deprecated and unsupported.
You can reference any single value numeric field in your expressions, for example: You can reference any single value numeric field in your expressions, for example: