-
Notifications
You must be signed in to change notification settings - Fork 25.6k
ES|QL: If there's no matching index to wildcard, list it as success #125173
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
Conversation
80e37e8 to
e1eee43
Compare
|
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
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, no specific suggestions. Nit: can you update the description? I know it might look self explanatory but it'd be nice for others/future.
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
Except - can you change the title and/or description to indicate that this is an ES|QL specific change, so that occurs in the commit message?
💚 Backport successful
|
…#125173) * If there's no matching index to wildcard, list it as success
|
Oops, read the comment too late, sorry... Will update the backport at least. |
#125506) * If there's no matching index to wildcard, list it as success
…#125173) * If there's no matching index to wildcard, list it as success
No description provided.