-
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](multi-catalog) Fix hive incorrect result by disable string dict filter if exprs contain null expr. #23361
[Fix](multi-catalog) Fix hive incorrect result by disable string dict filter if exprs contain null expr. #23361
Conversation
clang-tidy review says "All clean, LGTM! 👍" |
079ffd8
to
9762303
Compare
clang-tidy review says "All clean, LGTM! 👍" |
run buildall |
(From new machine)TeamCity pipeline, clickbench performance test result: |
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. |
9762303
to
55db1b2
Compare
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
… filter if exprs contain null expr.
55db1b2
to
95e55ac
Compare
run buildall |
clang-tidy review says "All clean, LGTM! 👍" |
(From new machine)TeamCity pipeline, clickbench performance test result: |
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. |
run external |
… filter if exprs contain null expr. (apache#23361) Issue Number: close apache#21960 Fix hive incorrect result by disable string dict filter if exprs contain null expr.
Proposed changes
Issue Number: close #21960
Fix hive incorrect result by disable string dict filter if exprs contain null expr.
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...