[DOCS] removed coming tags from scripting docs
This commit is contained in:
parent
18b02d58a4
commit
425ea5bca6
|
@ -242,8 +242,6 @@ on your box or not.
|
||||||
|
|
||||||
deprecated[1.6.0, the `script.disable_dynamic` setting is deprecated in favour of fine-grained settings described as follows]
|
deprecated[1.6.0, the `script.disable_dynamic` setting is deprecated in favour of fine-grained settings described as follows]
|
||||||
|
|
||||||
coming[1.6.0, Fine-grained script settings replace the `script.disable_dynamic` setting]
|
|
||||||
|
|
||||||
It is possible to enable scripts based on their source, for
|
It is possible to enable scripts based on their source, for
|
||||||
every script engine, through the following settings that need to be added to the
|
every script engine, through the following settings that need to be added to the
|
||||||
`config/elasticsearch.yml` file on every node.
|
`config/elasticsearch.yml` file on every node.
|
||||||
|
@ -286,7 +284,7 @@ NOTE: Global scripting settings affect the `mustache` scripting language.
|
||||||
<<search-template,Search templates>> internally use the `mustache` language,
|
<<search-template,Search templates>> internally use the `mustache` language,
|
||||||
and will still be enabled by default as the `mustache` engine is sandboxed,
|
and will still be enabled by default as the `mustache` engine is sandboxed,
|
||||||
but they will be enabled/disabled according to fine-grained settings
|
but they will be enabled/disabled according to fine-grained settings
|
||||||
specified in `elasticsearch.yml`. coming[1.6.0, `mustache` scripts were previously always on regardless of whether dynamic scripts were enabled or not]
|
specified in `elasticsearch.yml`.
|
||||||
|
|
||||||
It is also possible to control which operations can execute scripts. The
|
It is also possible to control which operations can execute scripts. The
|
||||||
supported operations are:
|
supported operations are:
|
||||||
|
|
Loading…
Reference in New Issue