Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Change the Parquet writer's
default_row_group_size_bytes
from 128MB to inf #16750Change the Parquet writer's
default_row_group_size_bytes
from 128MB to inf #16750Changes from 13 commits
8ad71f8
6750d75
dd599ce
3e723b8
e994116
01c4a17
e1a6b13
511eb20
d2051e7
e95b96c
26af59f
ad1cbac
c5e81fe
135d565
94fb993
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
with the new value, does row_group_size_bytes_val_in_mb and its use still make sense?
Also, should we change the Python default to None? In C++ it would be a breaking change, but Python does not have this limitation.
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.
None
makes the most sense on the Python side. Let's wait for Spark to let us know if they want a specific value in bytes or if infinity (None) is good to go.