feat(datafusion): use pyarrow for type conversion #9299
Merged
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.
Description of changes
This PR moves datafusion type system conversion to use PyArrow, which is much
more robust than the SQL hacking we've been doing.
I've added two new methods to support this, required to workaround datafusion inconsistencies in output types:but also potentially useful for ClickHouse
DataType._as_nullable
: returns a nullable version of the type, recursively converting for nested types.DataType._as_non_nullable
: similar to_as_nullable
but going the other direction, making everything non-nullable.Two analogous methods have been added toSchema
as well.Unit tests are included, including a hypothesis test to cover as many datatypes as possible.
This now is specific to datafusion to avoid an unnecessary maintenance burden for functionality that might never be used.