-
Notifications
You must be signed in to change notification settings - Fork 4.7k
HIVE-28765: Iceberg: Incorrect partition statistics on time travel + partition evolution #5748
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
base: master
Are you sure you want to change the base?
Conversation
c33a0d6
to
7b1b1b8
Compare
7b1b1b8
to
6caf105
Compare
6caf105
to
01a4117
Compare
…partition evolution
01a4117
to
e11c40d
Compare
|
@@ -2149,12 +2149,16 @@ public List<Partition> getPartitions(org.apache.hadoop.hive.ql.metadata.Table hm | |||
} | |||
|
|||
public boolean isPartitioned(org.apache.hadoop.hive.ql.metadata.Table hmsTable) { | |||
if ((hmsTable.getAsOfVersion() != null || hmsTable.getAsOfTimestamp() != null) && | |||
hasUndergonePartitionEvolution(hmsTable) || |
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.
I used IcebergTableUtil.getTableSnapshot
to avoid duplicate knowledge of the snapshot configurations. I can move it back to the original style if we prefer it.
What changes were proposed in this pull request?
https://issues.apache.org/jira/browse/HIVE-28765
We use not partition stats but table stats when we access a complicated table with tagging or branching.
Why are the changes needed?
We would like to improve the query plan for a time-travel read with tagging and branching.
Does this PR introduce any user-facing change?
No
Is the change a dependency upgrade?
No
How was this patch tested?
Updated an existing query file.