Skip to content

[9.0] ESQL: Reuse child outputSet inside the plan where possible (#124611) #125275

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

Merged
merged 1 commit into from
Mar 20, 2025

Conversation

costin
Copy link
Member

@costin costin commented Mar 20, 2025

Backports the following commits to 9.0:

…24611)

Avoid creating outputSet between nodes that passthrough their input

Relates elastic#124395
@costin costin added :Analytics/ES|QL AKA ESQL >enhancement auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) labels Mar 20, 2025
@elasticsearchmachine elasticsearchmachine merged commit 4b4c2d3 into elastic:9.0 Mar 20, 2025
16 checks passed
@costin costin deleted the backport/9.0/pr-124611 branch March 20, 2025 03:55
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 >enhancement Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v9.0.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants