-
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
Ensure the field exists in the index pattern before grabbing it #20639
Ensure the field exists in the index pattern before grabbing it #20639
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
Jenkins, test this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks!
💔 Build Failed |
It looks like the build failed because of the test that was disabled in #20637. I rebased against master to pick up the disable change. |
jenkins, test this |
💚 Build Succeeded |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks @trevan, I'll backport this to the 6.x branch as well.
I noticed that when I upgraded to 6.3, sometimes my filter bars were missing. After tracking it down, it looks like the filter bars were using old fields that have been removed from the index pattern.
Since Kibana already checks for the existence of the index pattern, I thought a simple check for the existence of the field would be nice as well. That way, the filter bar will still show up no matter if the index pattern or the field name is bad.