-
Notifications
You must be signed in to change notification settings - Fork 406
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: use table config target file size, expose target_file_size in python #2811
fix: use table config target file size, expose target_file_size in python #2811
Conversation
1893da3
to
42f73b1
Compare
Pull request was converted to draft
aee6132
to
0388ab6
Compare
crates/core/src/operations/mod.rs
Outdated
/// Get the target_file_size from the table configuration in the sates | ||
/// If table_config does not exist (only can occur in the first write action) it takes | ||
/// the configuration that was passed to the writerBuilder. | ||
pub fn get_target_file_size( |
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 don't think this should become part of our public API, so I'm going to slap a crate level visibility on it.
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.
Woops, my bad, should have been internal indeed
0388ab6
to
452f8a3
Compare
452f8a3
to
60a1080
Compare
Description
If the target_file_size is None but we have a snapshot, then we should take it from the table config, otherwise we try to fetch it from the provided configuration since the setting might be in there.
If you pass delta.targetFileSize to the configuration, this will be used even on first writes. Additionally target_file_size can be passed to the rust writer, which takes precedence over any table config that has been set
Related issues