-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable scripted fields when dynamic scripting is disabled #2989
Comments
Using Kibana 4-b3 with disabled dynamic scripting in ES goes directly to huge exception after index is defined in settings. This is quite frustrating if you do not expect this. Also, some installations (like mine is) dynamic scripting is wanted to remain disabled. If someone wants to just experiment with ES/Kibana, and reads "Download, Extract, Awesome" on download page, then this is not where one wants to end on its first journey. The exception goes like this
|
New to the ELK, stack it took me several hours to figure out the cause of this exception. It was that I had (as advised by many how to) disabled dynamic scripting. If it can help here is the complete Exception :
|
As part of #7700 we added a check to disable creation of new scripted fields in the interface if dynamic scripting is disabled: 9563f26 However, keeping this ticket open for this part:
|
It's been over 2 years since the last comment on this issue. We've switched to Painless scripting language. I suppose you could disable that in Elasticsearch? I'm going to close but if this is still an issue please reopen and elaborate. |
Assuming we can check the cluster state for dynamic scripting support, we should at the very least disable the scripted fields interface when it's disabled.
Ideally, we should scrub all requests of any scripted fields that may be defined, possibly previous to the dynamic scripting being disabled.
The text was updated successfully, but these errors were encountered: