Uh oh!
There was an error while loading. Please reload this page.
[Fix](inverted index) fix wrong no need read data when same column in inverted index and like function - #36687
Conversation
… inverted index and like function
doris-robot
commented
Jun 21, 2024
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
airborne12
commented
Jun 21, 2024
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
doris-robot
commented
Jun 21, 2024
TeamCity be ut coverage result: |
doris-robot
commented
Jun 21, 2024
TPC-H: Total hot run time: 39593 ms |
doris-robot
commented
Jun 21, 2024
TPC-DS: Total hot run time: 174602 ms |
doris-robot
commented
Jun 21, 2024
ClickBench: Total hot run time: 30.77 s |
… inverted index and like function (#36687) ## Proposed changes SQL like SELECT COUNT() FROM table WHERE a >= '2024-06-15 00:00:00' AND b LIKE '%xxx%' AND b MATCH 'xxx' for inverted index tables may cause incorrect optimization in the segment iterator, leading to the no-read-data optimization being applied incorrectly.
… inverted index and like function (apache#36687) ## Proposed changes SQL like SELECT COUNT() FROM table WHERE a >= '2024-06-15 00:00:00' AND b LIKE '%xxx%' AND b MATCH 'xxx' for inverted index tables may cause incorrect optimization in the segment iterator, leading to the no-read-data optimization being applied incorrectly.
… inverted index and like function (apache#36687) ## Proposed changes SQL like SELECT COUNT() FROM table WHERE a >= '2024-06-15 00:00:00' AND b LIKE '%xxx%' AND b MATCH 'xxx' for inverted index tables may cause incorrect optimization in the segment iterator, leading to the no-read-data optimization being applied incorrectly.
… inverted index and like function apache#36687 (apache#38651) cherry pick from apache#36687
… inverted index and like function (apache#36687) ## Proposed changes SQL like SELECT COUNT() FROM table WHERE a >= '2024-06-15 00:00:00' AND b LIKE '%xxx%' AND b MATCH 'xxx' for inverted index tables may cause incorrect optimization in the segment iterator, leading to the no-read-data optimization being applied incorrectly.
Proposed changes
SQL like SELECT COUNT() FROM table WHERE a >= '2024-06-15 00:00:00' AND b LIKE '%xxx%' AND b MATCH 'xxx' for inverted index tables may cause incorrect optimization in the segment iterator, leading to the no-read-data optimization being applied incorrectly.