Add ExtensionType trait and CanonicalExtensionType enum#5822
Merged
alamb merged 25 commits intoapache:mainfrom Feb 2, 2025
Merged
Add ExtensionType trait and CanonicalExtensionType enum#5822alamb merged 25 commits intoapache:mainfrom
ExtensionType trait and CanonicalExtensionType enum#5822alamb merged 25 commits intoapache:mainfrom
Conversation
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.
Rationale for this change
It would be nice to better support reading and writing the Arrow canonical
uuidandjsonextension types with the arrow and parquet crate i.e. mapping between the arrow extension type and the parquet logicaluuidandjsontypes.What changes are included in this PR?
This adds an
ExtensionTypetrait, some impls for canonical extension types and aCanonicalExtensionTypeenum for canonical extension types.Are there any user-facing changes?
Users can now annotate their fields with extension types, and for
uuidandjsonthey are propagated via the arrow writer to map to the parquetuuidandjsonlogical types.