-
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
Scripted Fields Lack Validation #5088
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Scripted Fields
Scripted fields features
Comments
panda01
added
the
bug
Fixes for quality problems that affect the customer experience
label
Oct 9, 2015
panda01
changed the title
Scripted Fields Lacks Validation
Scripted Fields Lack Validation
Oct 9, 2015
Discovered while messing with #4594. |
Labeling low fruit because I think we can simply use the scripted field and see if we get an error from Elasticsearch when we try, but it may be more complicated than that. |
closed by #20746 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Scripted Fields
Scripted fields features
When creating a scripted field, if you use a field that isn't a numeral, when you go to discover Kibana just kind of barfs on itself.
Since we can get the field types from ES, i think we should use those to help the user along with making them.
Also, When you input a non valid value into the formatters, no error is thrown, or anything indicating that that value, will not work.
This probably will need to be broken down, into two actionable tasks.
Repro
The text was updated successfully, but these errors were encountered: