-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
planner: fix bug for logical rule outer join elimination #13947
planner: fix bug for logical rule outer join elimination #13947
Conversation
/run-all-tests |
Codecov Report
@@ Coverage Diff @@
## master #13947 +/- ##
===========================================
Coverage 80.2047% 80.2047%
===========================================
Files 482 482
Lines 120741 120741
===========================================
Hits 96840 96840
Misses 16180 16180
Partials 7721 7721 |
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
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
@@ -199,7 +199,10 @@ func (o *outerJoinEliminator) doOptimize(p LogicalPlan, aggCols []*expression.Co | |||
parentCols = append(parentCols, expression.ExtractColumns(expr)...) | |||
} | |||
case *LogicalAggregation: | |||
parentCols = append(parentCols[:0], x.groupByCols...) |
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.
A question won't block merging this pr: could we just remove the groupByCols
from the Aggregation
?
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.
I think we can't. groupByCols
are used to check whether aggregation can keep order when generating stream agg.
/merge |
/run-all-tests |
cherry pick to release-3.0 failed |
What problem does this PR solve?
What is changed and how it works?
The aggregation group by columns shouldn't be
groupByCols
, instead of it, it should beexpression.ExtractColumns(groupByItems)
.Check List
Tests