[Fix](inverted index) fix wrong no need read data when same column in inverted index and like function #36687
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… inverted index and like function
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
Member
Author
|
run buildall |
Contributor
|
clang-tidy review says "All clean, LGTM! 👍" |
github-actions
bot
added
the
approved
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
|
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 39593 ms |
TPC-DS: Total hot run time: 174602 ms |
ClickBench: Total hot run time: 30.77 s |
dataroaring
pushed a commit
that referenced
this pull request
Jun 21, 2024
… 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.
airborne12
added a commit
to airborne12/apache-doris
that referenced
this pull request
Jul 31, 2024
… 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.
airborne12
added a commit
to airborne12/apache-doris
that referenced
this pull request
Aug 1, 2024
… 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.
mongo360
pushed a commit
to mongo360/doris
that referenced
this pull request
Dec 11, 2024
… inverted index and like function apache#36687 (apache#38651) cherry pick from apache#36687
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.