Skip to content

Conversation

@ivancea
Copy link
Contributor

@ivancea ivancea commented Nov 28, 2024

Manual 8.x backport of #114317

Auto-backport failed with a conflict on muted-tests.yml

@ivancea ivancea added >non-issue backport Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) :Analytics/ES|QL AKA ESQL v8.18.0 labels Nov 28, 2024
@github-actions
Copy link
Contributor

Documentation preview:

@ivancea ivancea added the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label Nov 28, 2024
@elasticsearchmachine elasticsearchmachine merged commit d90b4c7 into elastic:8.x Nov 28, 2024
16 checks passed
@ivancea ivancea deleted the backport-categorize-blockhash branch November 28, 2024 11:48
elasticsearchmachine pushed a commit that referenced this pull request Dec 3, 2024
Fix #117770 Fix
#117784

#117699 made changes to how
we plan aggregations which were supposed to only trigger when a query
contained a `CATEGORIZE`, but accidentally changed a code path that
seems to only be required for interoperability with pre-8.13 nodes.
Because of this, we didn't notice failing tests until the periodic bwc
tests ran.

The code this PR fixes addresses situations where `Aggregate` plan nodes
contained _aliases inside the aggregates_. On `main` and `8.x`, this is
effectively an illegal state: since
#104958, aliases in the
aggregates become `Eval` nodes before and after the `Aggregate` node.

But here, on 8.x, we'll just fix this code path so that it behaves
exactly as before #117699.

If this passes the full-bwc test, I plan to forward-port this by
removing the obsolete code path on `main`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Analytics/ES|QL AKA ESQL auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport >non-issue Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v8.18.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants