-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[BugFix] fix uncorrect logical properties when apply LowCardinality optimize #11793
Conversation
run starrocks_admit_test |
run starrocks_admit_test |
run starrocks_fe_unittest |
ee9abd8
to
fae0561
Compare
run starrocks_admit_test |
run starrocks_admit_test |
fae0561
to
96b76f2
Compare
run starrocks_admit_test |
1 similar comment
run starrocks_admit_test |
run starrocks_admit_test |
run starrocks_admit_test |
run starrocks_admit_test |
Kudos, SonarCloud Quality Gate passed! |
[FE PR Coverage Check]😍 pass : 65 / 66 (98.48%) file detail
|
https://github.com/Mergifyio backport branch-2.4 |
✅ Backports have been created
|
https://github.com/Mergifyio backport branch-2.3 branch-2.2 |
…ptimize (#11793) we should rewrite logical property after OptExpression rewrite (cherry picked from commit 2ac5807) # Conflicts: # fe/fe-core/src/main/java/com/starrocks/sql/optimizer/rule/tree/AddDecodeNodeForDictStringRule.java # fe/fe-core/src/main/java/com/starrocks/sql/plan/ScalarOperatorToExpr.java # fe/fe-core/src/test/java/com/starrocks/sql/plan/LowCardinalityTest.java
✅ Backports have been created
|
…ptimize (StarRocks#11793) we should rewrite logical property after OptExpression rewrite
…ptimize (#11793) we should rewrite logical property after OptExpression rewrite
What type of PR is this:
Which issues of this PR fixes :
Fixes #9104
Problem Summary(Required) :
we should rewrite logical property after OptExpression rewrite
Checklist: