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] Unhandled error on non existing policy #100593
Labels
:Analytics/ES|QL
AKA ESQL
>bug
ES|QL-ui
Impacts ES|QL UI
Team:QL (Deprecated)
Meta label for query languages team
Comments
dej611
added
>bug
Team:QL (Deprecated)
Meta label for query languages team
needs:triage
Requires assignment of a team area label
:Analytics/ES|QL
AKA ESQL
ES|QL-ui
Impacts ES|QL UI
labels
Oct 10, 2023
elasticsearchmachine
removed
the
needs:triage
Requires assignment of a team area label
label
Oct 10, 2023
Pinging @elastic/es-ql (Team:QL) |
Pinging @elastic/elasticsearch-esql (:Query Languages/ES|QL) |
This looks like a validation error that can be caught by the verifier. |
costin
added a commit
to costin/elasticsearch
that referenced
this issue
Oct 10, 2023
When dealing with non-existing policies, the validation code kept trying to determine the matching field resulting in a NPE. Fix elastic#100593
costin
added a commit
to costin/elasticsearch
that referenced
this issue
Oct 10, 2023
…lastic#100647) When dealing with non-existing policies, the validation code kept trying to determine the matching field resulting in a NPE. Fix elastic#100593
elasticsearchmachine
pushed a commit
that referenced
this issue
Oct 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Analytics/ES|QL
AKA ESQL
>bug
ES|QL-ui
Impacts ES|QL UI
Team:QL (Deprecated)
Meta label for query languages team
Elasticsearch Version
8.11.0
Installed Plugins
No response
Java Version
bundled
OS Version
MacOS
Problem Description
When sending a ESQL query with the
enrich
command that involves a policy that does not existing aNullPointerException
is thrown and shown as error messages to the user:Query:
Returns:
Steps to Reproduce
See above.
Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: