ESQL: Support StubRelation with empty output in PropagateEmptyRelation
#136959
+91
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR extends the
PropagateEmptyRelationoptimizer rule to handleStubRelationnodes with empty output, in addition to the existingLocalRelationsupport.Previously, when using
INLINE STATSafter dropping all fields (such asROW a = 12 | drop a | inline stats b = count(*)), the optimizer would create aStubRelationwith empty output but fail to properly optimize aggregations over it. ThePropagateEmptyRelationrule now checks for bothLocalRelationwith empty supplier andStubRelationwith empty output, allowing correct optimization of aggregations in these scenarios.Closes #136851