-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Fix the misuse of star-tree when all predicates are always false under OR #12003
Fix the misuse of star-tree when all predicates are always false under OR #12003
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #12003 +/- ##
============================================
- Coverage 61.65% 61.62% -0.04%
Complexity 1150 1150
============================================
Files 2385 2385
Lines 129250 129251 +1
Branches 20007 20009 +2
============================================
- Hits 79690 79645 -45
- Misses 43748 43809 +61
+ Partials 5812 5797 -15
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
f12cefd
to
3a37769
Compare
@@ -78,7 +78,8 @@ private GroupByOperator buildNonFilteredGroupByPlan() { | |||
|
|||
// Use star-tree to solve the query if possible | |||
List<StarTreeV2> starTrees = _indexSegment.getStarTrees(); | |||
if (starTrees != null && !_queryContext.isSkipStarTree()) { | |||
if (!_queryContext.isNullHandlingEnabled() && !filterOperator.isResultEmpty() && starTrees != null |
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.
so we were missing null handling enable flag before as well here? :-P
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.
Unfortunately yes..
Fix #11718
Fixes 2 scenarios where star-tree shouldn't be used: