-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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] (inverted index) fix query errors caused by ignore_above #37679
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! 👍" |
1 similar comment
clang-tidy review says "All clean, LGTM! 👍" |
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 anyone and no changes requested. |
TPC-H: Total hot run time: 40070 ms
|
TPC-DS: Total hot run time: 175586 ms
|
ClickBench: Total hot run time: 30.86 s
|
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. |
…e#37679) ## Proposed changes If the written value exceeds ignore_above, it will be written as null. The queried value exceeds ignore_above means the written value cannot be found. The query needs to be downgraded to read from the segment file.
## Proposed changes If the written value exceeds ignore_above, it will be written as null. The queried value exceeds ignore_above means the written value cannot be found. The query needs to be downgraded to read from the segment file.
…pache#37686) ## Proposed changes pick from master apache#37679
Proposed changes
If the written value exceeds ignore_above, it will be written as null.
The queried value exceeds ignore_above means the written value cannot be found.
The query needs to be downgraded to read from the segment file.
Issue Number: close #xxx