Avoid Upcasting to pa.large_binary()
#803
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pa.large_binary()
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #791
Parquet seems to have a 2GB upper limit on the size of a single Page within each column. Attempting to write data that is larger than 2GB in a single cell/page results in errors observed in the issue linked above.
This PR seeks to limit
schema_to_pyarrowto cast to regular types that restrict Arrow data representations to 2GB, which aligns with the limitations of Parquet.EDIT:
Based on the discussions on #791 it looks like we'd benefit from decoupling the motivation to support larger arrow types from the size limitations of parquet.
#807 resolves the schema inconsistency issue by always casting to
large_*types instead