-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Remove the single asterisk when converting queries to user side #10280
Conversation
Can one of the admins verify this patch? |
Hmmm that's an odd error in the Selenium tests, doesn't look related to the changes to me. @LeeDr have you seen that one before? Functionality LGTM. @lukasolson could you give it a sanity check as well? Since you've been around longer you might know of a reason why |
@Bargs the current build failure for this PR isn't in the Selenium tests. Goes to this elastic+kibana+pull-request+multijob-intake job: https://kibana-ci.elastic.co/job/elastic+kibana+pull-request+multijob-intake/4004/console Which shows:
|
Whoops, my bad @LeeDr, missing the obvious. It looked like Intern output to me for some reason. |
Tests passed locally :/ perhaps it was a timing issue. jenkins, test this |
This is probably a fine first step, but what I'd really like to see is when the user hasn't entered any query, default to using |
@lukasolson agreed, we should update that in the future. @trevan thanks for the contribution! |
@lukasolson, I created a pull request to use match_all instead of asterisk #10350. Is that what you were thinking? |
Fixes #10272.
This removes the single * when parsing a query for human consumption. That affects the search bars in visualization, dashboard, and discover so that it shows the placeholder text the first time you load the page.
There is one place that uses parseQuery directive and doesn't have a placeholder. It is in the filters buckets in visualization. Should there be a placeholder there now that the * won't appear initially?