-
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
DROP of EVAL planning issues #107083
Labels
Comments
elasticsearchmachine
added
the
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
label
Apr 4, 2024
Pinging @elastic/es-analytical-engine (Team:Analytics) |
costin
added a commit
to costin/elasticsearch
that referenced
this issue
Apr 5, 2024
Recursive aliases (eval x = 1, x1 = x) were not taken into account when combining projections causing the target field to be lost (and only the immediate intermediate named expression to be used instead which became invalid). Fix elastic#107083
costin
added a commit
that referenced
this issue
Apr 5, 2024
Recursive aliases (eval x = 1, x1 = x) were not taken into account when combining projections causing the target field to be lost (and only the immediate intermediate named expression to be used instead which became invalid). Fix #107083
costin
added a commit
to costin/elasticsearch
that referenced
this issue
Apr 5, 2024
Recursive aliases (eval x = 1, x1 = x) were not taken into account when combining projections causing the target field to be lost (and only the immediate intermediate named expression to be used instead which became invalid). Fix elastic#107083 (cherry picked from commit a9388e1)
Re-opening as I found another reproducer:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
And without aggs
The text was updated successfully, but these errors were encountered: