-
Notifications
You must be signed in to change notification settings - Fork 25.6k
ES|QL: fix ENRICH validation for use of wildcards #121911
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: fix ENRICH validation for use of wildcards #121911
Conversation
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
|
Hi @luigidellaquila, I've created a changelog YAML for you. |
| if (ne instanceof UnresolvedNamePattern || ne instanceof UnresolvedStar) { | ||
| var src = ne.source(); | ||
| throw new ParsingException(src, "Using wildcards [*] in ENRICH WITH projections is not allowed [{}]", up.pattern()); | ||
| throw new ParsingException(src, "Using wildcards [*] in ENRICH WITH projections is not allowed [{}]", src.text()); |
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.
| throw new ParsingException(src, "Using wildcards [*] in ENRICH WITH projections is not allowed [{}]", src.text()); | |
| throw new ParsingException(src, "Using wildcards [*] in ENRICH WITH projections is not allowed, found [{}]", src.text()); |
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. Left one minor styling comment.
…d_validation' into esql/fix_enrich_wildcard_validation
|
Thanks folks! |
Fixes: #121740
Fix validation of ENRICH with usage of (unsupported) wildcards in field names, eg.