Uh oh!
There was an error while loading. Please reload this page.
[fix](inverted index) Fix errors caused by enable_need_read_data_opt - #42064
Conversation
doris-robot
commented
Oct 18, 2024
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
csun5285
commented
Oct 18, 2024
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
doris-robot
commented
Oct 18, 2024
TeamCity be ut coverage result: |
bf9369d to
0ba83baComparecsun5285
commented
Oct 20, 2024
run buildall |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
…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.
…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.