Today, scripted fields in Kibana support only Lucene expressions, which makes sense as this is the default scripting language in Elasticsearch. However, user can turn on other scripting languages in Elasticsearch, including Painless coming in 5.0.
In order for someone to experiment with these non-default languages, one has to modify the Kibana source or resort to unintuitive workarounds (e.g. here).
The ask here is to provide a supported way to create scripted fields in Kibana that run scripts in non-default languages.
Note: A while ago a user submitted a PR to add a "lang" parameter to scripted fields, but we felt that w/o additional support in Elasticsearch, the approach proposed was not sufficiently robust.
Today, scripted fields in Kibana support only Lucene expressions, which makes sense as this is the default scripting language in Elasticsearch. However, user can turn on other scripting languages in Elasticsearch, including Painless coming in 5.0.
In order for someone to experiment with these non-default languages, one has to modify the Kibana source or resort to unintuitive workarounds (e.g. here).
The ask here is to provide a supported way to create scripted fields in Kibana that run scripts in non-default languages.
Note: A while ago a user submitted a PR to add a "lang" parameter to scripted fields, but we felt that w/o additional support in Elasticsearch, the approach proposed was not sufficiently robust.