-
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
[courier/rootSearchSource] stop loading the defaultIndexPattern #11012
[courier/rootSearchSource] stop loading the defaultIndexPattern #11012
Conversation
This appears to close #9028 EDIT: Maybe not actually... I can't get 9028 to happen locally at all, even in master, so I don't think this actually closes it. But it may already be closed. |
@spalger I'm not sure what this is fixing exactly. I can't get an error state in master that this would seem to resolve. How should we be testing this fix? And does it close any open issues? |
@w33ble @BigFunger This doesn't outright fix any issue, it just removes an "optimization" in favor of only loading Consider this scenario:
This doesn't fix the issue if the user tried to use the index pattern, or loaded up discover with a default index, but it does remove the useless loading of the default index pattern. |
@spalger can you rebase/merge on master, please? |
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
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.
Thanks for the explanation. LGTM.
Kibana uses a
rootSearchSource
to define the global search context (things like the time filter). ThissearchSource
has historically been assigned the default index pattern, but as far as I can tell this behavior is not utilized or desired and this PR removes it. NowsearchSources
must define the index they are intended for in order to be fetch-able.