Scripting: Allow to define scripts within config/scripts, automatically compiled and can be referenced by name
#429
Labels
Comments
|
Scripting: Allow to define scripts within |
medcl
pushed a commit
to medcl/elasticsearch
that referenced
this issue
Jul 1, 2011
…ally compiled and can be referenced by name, closes elastic#429.
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
Fix conditionals introduced in elastic#412 and others
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
…quest elastic#429) test21.tfvars redis and ems_redis to cache.t4g.micro * test21.tfvars redis and ems_redis to cache.t4g.micro Approved-by: Can Yildiz
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Allow to provide scripts to be precompiled on node startup within the
config/scriptsdirectory. Scripts end with the common lang extension (mvel,js,py,groovy).The name of a script is the name of the file, prefixed by internal directories. For example, if the script exists in
config/scripts/group1/group2/test.py, the script name will begroup1_group2_test.The script name can then be used in any element that accepts a script, replacing the actual script content.
The text was updated successfully, but these errors were encountered: