OpenSearch/docs/reference/migration/migrate_6_0/scripting.asciidoc

[[breaking_60_scripting_changes]]
=== Scripting changes

==== Groovy, JavaScript, and Python languages removed

The Groovy, JavaScript, and Python scripting languages were deprecated in
elasticsearch 5.0 and have now been removed. Use painless instead.

==== Native scripts removed

Native scripts have been removed. Instead,
<<modules-scripting-engine, implement a `ScriptEngine`>>.

==== Date fields now return dates

`doc.some_date_field.value` now returns ++ReadableDateTime++s instead of
milliseconds since epoch as a `long`. The same is true for
`doc.some_date_field[some_number]`. Use `doc.some_date_field.value.millis` to
fetch the milliseconds since epoch if you need it.

==== Removed access to index internal via the _index variable

The `_index` variable has been removed. If you used it for advanced scoring, consider writing a `Similarity` plugin.

==== Script Settings

All of the existing scripting security settings have been removed.  Instead
they are replaced with `script.allowed_types` and `script.allowed_contexts`.
Remove groovy scripting language (#21607) * Scripting: Remove groovy scripting language Groovy was deprecated in 5.0. This change removes it, along with the legacy default language infrastructure in scripting. 2016-11-22 19:24:12 -08:00			`[[breaking_60_scripting_changes]]`
			`=== Scripting changes`

Added removal of JavaScript and Python to breaking changes 2017-05-05 11:52:57 +02:00			`==== Groovy, JavaScript, and Python languages removed`
Remove groovy scripting language (#21607) * Scripting: Remove groovy scripting language Groovy was deprecated in 5.0. This change removes it, along with the legacy default language infrastructure in scripting. 2016-11-22 19:24:12 -08:00
Added removal of JavaScript and Python to breaking changes 2017-05-05 11:52:57 +02:00			`The Groovy, JavaScript, and Python scripting languages were deprecated in`
			`elasticsearch 5.0 and have now been removed. Use painless instead.`
Make dates be ReadableDateTimes in scripts (#22948) Instead of longs. If you want millis since epoch you can call doc.date_field.value.millis. Relates to #22875 2017-02-06 16:44:56 -05:00
Scripting: Remove native scripts (#24726) Native scripts have been replaced in documentation by implementing a ScriptEngine and they were deprecated in 5.5.0. This commit removes the native script infrastructure for 6.0. closes #19966 2017-05-17 14:49:24 -07:00			`==== Native scripts removed`

			`Native scripts have been removed. Instead,`
			<<modules-scripting-engine, implement a `ScriptEngine`>>.

Make dates be ReadableDateTimes in scripts (#22948) Instead of longs. If you want millis since epoch you can call doc.date_field.value.millis. Relates to #22875 2017-02-06 16:44:56 -05:00			`==== Date fields now return dates`

Update scripting.asciidoc Fixed bad asciidoc 2017-03-16 19:37:38 -07:00			`doc.some_date_field.value` now returns ++ReadableDateTime++s instead of
Make dates be ReadableDateTimes in scripts (#22948) Instead of longs. If you want millis since epoch you can call doc.date_field.value.millis. Relates to #22875 2017-02-06 16:44:56 -05:00			milliseconds since epoch as a `long`. The same is true for
			`doc.some_date_field[some_number]`. Use `doc.some_date_field.value.millis` to
			`fetch the milliseconds since epoch if you need it.`
Add New Security Script Settings (#24637) Settings are simplified to allowed_types and allowed_contexts. If a setting is not specified the default is to enable all for that setting. 2017-05-15 13:37:46 -07:00
Remove script access to term statistics (#19462) In scripts (at least some of the languages), the terms dictionary and postings can be access with the special _index variable. This is for very advanced use cases which want to do their own scoring. The problem is segment level statistics must be recomputed for every document. Additionally, this is not friendly to the terms index caching as the order of looking up terms should be controlled by lucene. This change removes _index from scripts. Anyone using it can and should instead write a Similarity plugin, which is explicitly designed to allow doing the calculations needed for a relevance score. closes #19359 2017-05-16 09:10:09 -07:00			`==== Removed access to index internal via the _index variable`

			The `_index` variable has been removed. If you used it for advanced scoring, consider writing a `Similarity` plugin.

Add New Security Script Settings (#24637) Settings are simplified to allowed_types and allowed_contexts. If a setting is not specified the default is to enable all for that setting. 2017-05-15 13:37:46 -07:00			`==== Script Settings`

Remove Deprecated Script Settings (#24756) Removes all fine-grained script settings replaced by scripts.types_allowed and scripts.contexts_allowed. 2017-05-18 13:32:46 -07:00			`All of the existing scripting security settings have been removed. Instead`
Remove script access to term statistics (#19462) In scripts (at least some of the languages), the terms dictionary and postings can be access with the special _index variable. This is for very advanced use cases which want to do their own scoring. The problem is segment level statistics must be recomputed for every document. Additionally, this is not friendly to the terms index caching as the order of looking up terms should be controlled by lucene. This change removes _index from scripts. Anyone using it can and should instead write a Similarity plugin, which is explicitly designed to allow doing the calculations needed for a relevance score. closes #19359 2017-05-16 09:10:09 -07:00			they are replaced with `script.allowed_types` and `script.allowed_contexts`.