-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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](hive) support partition prune for _HIVE_DEFAULT_PARTITION_ #31736
Conversation
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
run buildall |
// If any partition key is hive default partition, return true. | ||
// Only used for hive table. | ||
public boolean isHiveDefaultPartition() { | ||
for (PartitionKey partitionKey : partitionKeys) { |
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.
isDefaultPartition() not need delete?
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.
No, isDefaultPartition()
is for other cases.
"default" partition is not "null" partition.
the _HIVE_DEFAULT_PARTITION_
is actually "null" partition in Doris
) 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
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
Further comments
If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...