[WIP] Experiment with DataFusion against Arrow with Extension DataType support #15663
+351
−275
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
github-actions
bot
added
sql
This was referenced Apr 9, 2025
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.
Which issue does this PR close?
Another experiment in pursuit of #12644
Rationale for this change
It has been suggested that adding an Extension member to the DataType enum will be disruptive to downstream projects, so I thought I'd give it a try.
This also includes a (hacky) update to Arrow 55 but I separeated the commits.
What changes are included in this PR?
I added enough to get this to build and will experiment with an example to see what is required of Arrow to get extension types passing through various components (or if it's already built-in).
Built against apache/arrow-rs#7398 .
Are these changes tested?
Not yet!