-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](inverted index) Fix errors caused by enable_need_read_data_opt #42064
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
Conversation
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
TeamCity be ut coverage result: |
bf9369d to
0ba83ba
Compare
|
run buildall |
airborne12
left a comment
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
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
fe/fe-core/src/main/java/org/apache/doris/nereids/rules/implementation/AggregateStrategies.java
Show resolved
Hide resolved
zzzxl1993
left a comment
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
…pache#42064) ## Proposed changes In the current backend implementation, it is not correctly handle counts when `is null` predicate exists, so we forbid the storage layer's count currently. for example: ``` select count(b) from test where b is null ``` When apply the is null filter, the result array will fill the default value of the column type and the count operator can not detect whether the result is null, so the count operator compute the wrong result.
…pache#42064) ## Proposed changes In the current backend implementation, it is not correctly handle counts when `is null` predicate exists, so we forbid the storage layer's count currently. for example: ``` select count(b) from test where b is null ``` When apply the is null filter, the result array will fill the default value of the column type and the count operator can not detect whether the result is null, so the count operator compute the wrong result.
Proposed changes
In the current backend implementation, it is not correctly handle counts when
is nullpredicate exists, so we forbid the storage layer's count currently.for example:
When apply the is null filter, the result array will fill the default value of the column type and the count operator can not detect whether the result is null, so the count operator compute the wrong result.