-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Index name pattern not present in the error message #63529
Labels
:Analytics/EQL
EQL querying
>bug
:Security/Security
Security issues without another label
Team:QL (Deprecated)
Meta label for query languages team
Team:Security
Meta label for security team
Comments
astefan
added
>enhancement
:Security/Security
Security issues without another label
labels
Oct 12, 2020
Pinging @elastic/es-security (:Security/Security) |
Pinging @elastic/es-ql (:Query Languages/EQL) |
elasticmachine
added
the
Team:QL (Deprecated)
Meta label for query languages team
label
Oct 19, 2020
As mentioned in a different GH issue touching the same area as this issue, I understand the meaning of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Analytics/EQL
EQL querying
>bug
:Security/Security
Security issues without another label
Team:QL (Deprecated)
Meta label for query languages team
Team:Security
Meta label for security team
During a REST IT test on a secured cluster, in case the index pattern is an inexistent index, the error message itself is stripped of the index being searched for resulting in a message of the form
{"error":{"root_cause":[{"type":"verification_exception","reason":"Found 1 problem\nline -1:-1: Unknown index [*,-*]"}]
for a search like/inexistent/_eql/search
whereas the expected is to have the index pattern in the error messge itself.The text was updated successfully, but these errors were encountered: