ElasticsearchScriptingUserSettings

Controls the different 'languages' (painless/mustache/expressions) supported by the Elasticsearch cluster, and the different ways they can be used (file, index, inline). More complex configurations need to be handled by leaving these blank and controlling instead in the user YAML or JSON

Properties

expressions_enabled (boolean)
(5.x+ only) If enabled (the default) then the expressions scripting engine is allowed for each of the enabled storage types ('stored', 'file', 'inline'). NOTES: (Corresponds to the parameters 'script.engine.expression.[file|stored|inline]')
file (ElasticsearchScriptTypeSettings)
Scripts can be stored in indexes ('stored'), or uploaded in file bundles ('file'), or used directly in API requests ('inline'). This object controls whether scripting is enabled for the given type, together with other fine grained control parameters.
inline (ElasticsearchScriptTypeSettings)
Scripts can be stored in indexes ('stored'), or uploaded in file bundles ('file'), or used directly in API requests ('inline'). This object controls whether scripting is enabled for the given type, together with other fine grained control parameters.
mustache_enabled (boolean)
(5.x+ only) If enabled (the default) then the mustache scripting engine is allowed for each of the enabled storage types ('stored', 'file', 'inline'). NOTES: (Corresponds to the parameters 'script.engine.mustache.[file|stored|inline]'); .mutache.inline. is not settable
painless_enabled (boolean)
(5.x+ only) If enabled (the default) then the painless scripting engine is allowed for each of the enabled storage types ('stored', 'file', 'inline'). NOTES: (Corresponds to the parameters 'script.engine.painless.[file|stored|inline]')
stored (ElasticsearchScriptTypeSettings)
Scripts can be stored in indexes ('stored'), or uploaded in file bundles ('file'), or used directly in API requests ('inline'). This object controls whether scripting is enabled for the given type, together with other fine grained control parameters.