-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[Scripted Fields] No inline scripting languages are shown #11959
Copy link
Copy link
Closed
Labels
Feature:Kibana ManagementFeature label for Data Views, Advanced Setting, Saved Object management pagesFeature label for Data Views, Advanced Setting, Saved Object management pagesFeature:Scripted FieldsScripted fields featuresScripted fields featuresimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.loe:smallSmall Level of EffortSmall Level of Effort
Metadata
Metadata
Assignees
Labels
Feature:Kibana ManagementFeature label for Data Views, Advanced Setting, Saved Object management pagesFeature label for Data Views, Advanced Setting, Saved Object management pagesFeature:Scripted FieldsScripted fields featuresScripted fields featuresimpact:lowAddressing this issue will have a low level of impact on the quality/strength of our product.Addressing this issue will have a low level of impact on the quality/strength of our product.loe:smallSmall Level of EffortSmall Level of Effort
Type
Fields
Give feedbackNo fields configured for issues without a type.
When users attempt to create a scripted field in Kibana, they are supposed to be shown a list of inline scripting languages enabled in Elasticsearch. This list used to show languages such as "painless" and "expression". Now (with the latest Elasticsearch
masterbuild) this list is empty:The list is populated by Kibana by calling the http://localhost:9200/_cluster/settings?include_defaults=true&filter_path=**.script.engine.*.inline Elasticsearch API at this point in the code.
This API call used to return a response like this:
The same API call now returns: