-
Notifications
You must be signed in to change notification settings - Fork 24.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
[ES|QL] - Using a wildcard "*" on a none existing index together with a existing index, then the user doesn't get an error from ES #104987
Comments
Pinging @elastic/es-analytical-engine (Team:Analytics) |
The ask here, as I understand it, is for ES|QL to fail the entire query if an index wild card returns zero results. That has the potential to break existing queries, so I've labeled this as a breaking change issue. |
The behavior can be customized by allowing the user to specify the preferred indices option. (Thanks to @astefan for pointing out). |
Documenting here all the current behaviours:
I do not mind either fail or make it fail silently as long as one index is available, the problem I see here is a lack of consistency. |
I agree, consistency makes sense here. I would think the default alignment of throwing an error due to a non-existent index makes sense in any combination regardless of expansion, but if that default is both expensive and inconsistent with defaults outside of ES|QL I'm interested in cost of the alternative(s). |
Linking here the work in progress: #106636 For the record, this would make a query where the index (without wildcard) name that doesn't exist to not generate an error. For example: For a query like |
Closing as fixed with #106636. |
Reopening after feature reverting in #108692. |
Elasticsearch Version
8.13
Installed Plugins
No response
Java Version
bundled
OS Version
MacOS - latest
Problem Description
When I use FROM with an index that does not exist together with a wildcard: "*" and an index that does exist, then Elasticsearch does not come back with errors, but Kibana does.
Example:
from kibana_sample_data_logs, noneexistingindex* | limit 10
Adding recording to show-case the error.
Steps to Reproduce
See the recording to re-produce.
Basically you go use this query:
from kibana_sample_data_logs, noneexistingindex* | limit 10
Skaermoptagelse.2024-01-31.kl.17.37.05.mov
,
Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: