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
[Datasets] Correct schema unification for Datasets with ragged Arrow arrays #31076
[Datasets] Correct schema unification for Datasets with ragged Arrow arrays #31076
Changes from 16 commits
921872d
d7a8472
e5094ef
9a962c8
2530d6a
2068d12
f4587a8
b33f8c9
ce43367
c5f2561
dc36c50
cadbf24
46e11fb
fb93cad
669fcd3
2f0bbe2
6efd914
b5d916c
94a4b8d
55704e6
8b60918
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.
This can be a future PR (I can do it as part of the type promotion PR), but we might want to try-except this
pyarrow.unify_schemas()
call, since this is the point at which we're validating that all of the schemas from different blocks are compatible. Propagating any exception raised frompyarrow.unify_schemas()
seems fine for now, and in the future we can look at wrapping any raised exceptions with our own error indicating that the blocks have incompatible schemas and giving the user a path to rectifying this (e.g. manually specifying a schema at read time, so all blocks are consistent).