-
Notifications
You must be signed in to change notification settings - Fork 344
feat: Support PartitionStats
#1111
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: main
Are you sure you want to change the base?
feat: Support PartitionStats
#1111
Conversation
…athanc-n/iceberg-rust into partition-statistics-handler
|
@Xuanwo @Fokko @sdd @liurenjie1024 This should be ready for review |
| Ok(()) | ||
| } | ||
|
|
||
| fn update_snapshot_info(&mut self, snapshot_id: i64, updated_at: i64) { |
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.
If we only use update_snapshot_info internally, is it better to have seperate APIs like update_with_data_file and refresh_with_snapshot?
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 believe its safer to just have update_snapshot_info kept like this because if users are going to update the statistics for the latest snapshot this should always be called alongside it. I think it is quite dangerous to not update to latest snapshot when updating because it is incorrect if the user forgets to call the API to refresh. It will also be used for other partition stat updates as seen in the java implementation here.
Which issue does this PR close?
Part of #1102
What changes are included in this PR?
Added partition stats outline
Are these changes tested?