-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Merged
clarkzinzow
merged 21 commits into
ray-project:master
from
scottjlee:ragged-arrow-schema
Jan 4, 2023
Merged
Changes from all commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
921872d
initial progress
d7a8472
more scratch work
e5094ef
add scalar_type property in ArrowTensorType to simplify unify_schemas…
9a962c8
clean up and format
2530d6a
add check for same type on simple blocks, lazy block list support
2068d12
format
f4587a8
Merge branch 'master' into ragged-arrow-schema
b33f8c9
Merge branch 'master' into ragged-arrow-schema
ce43367
improved typechecking on unify_schemas
c5f2561
check all blocks for potential pyarrow schema
dc36c50
Merge branch 'master' into ragged-arrow-schema
cadbf24
comments
46e11fb
Merge branch 'master' into ragged-arrow-schema
fb93cad
additional unit tests
669fcd3
comments, format, clean up
2f0bbe2
Merge branch 'master' into ragged-arrow-schema
6efd914
final comments and format
b5d916c
Merge branch 'master' into ragged-arrow-schema
94a4b8d
Merge branch 'master' into ragged-arrow-schema
55704e6
defer pyarrow import to unify_schemas func
8b60918
Merge branch 'master' into ragged-arrow-schema
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
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).