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](catalog) fix hive partition prune bug on nereids #23026
Conversation
138a082
to
f51ab76
Compare
run buildall |
(From new machine)TeamCity pipeline, clickbench performance test result: |
f51ab76
to
c6e6bd8
Compare
run buildall |
c6e6bd8
to
06a06c2
Compare
run buildall |
1 similar comment
run buildall |
06a06c2
to
4437b0d
Compare
run buildall |
(From new machine)TeamCity pipeline, clickbench performance test result: |
LGTM |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
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
…che#31736) This PR apache#23026 support the partition prune for hive table with `_HIVE_DEFAULT_PARTITION`, but it will always select partition with `_HIVE_DEFAULT_PARTITION`. This PR apache#31613 support null partition for olap table's list partition, so we can treat `_HIVE_DEFAULT_PARTITION` as null partition of hive table. So this PR change the partition prune logic
) This PR #23026 support the partition prune for hive table with `_HIVE_DEFAULT_PARTITION`, but it will always select partition with `_HIVE_DEFAULT_PARTITION`. This PR #31613 support null partition for olap table's list partition, so we can treat `_HIVE_DEFAULT_PARTITION` as null partition of hive table. So this PR change the partition prune logic
Proposed changes
Nereids uses different partition pruner to prune the partition.
The new partition pruner support predicate like
cast(day1 as date) > cast("2023-08-16" as date)
This PR mainly changes:
count(*)
in hive table.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...