fix(parquet): Reading UUID columns#173
Merged
zeroshade merged 3 commits intoapache:mainfrom Oct 26, 2024
Merged
Conversation
joellubi
approved these changes
Oct 26, 2024
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Split from #171 to be a more focused PR.
Currently we will properly write arrow data with the canonical UUID extension type as a parquet UUID column via
pqarrow. This PR enables us to read back that data using theextensions.UUIDdata type correctly even when we don't have a stored schema.Added a test to the
ArrowExtensionTypeRoundTripto ensure proper round trip without a stored schema.