Skip to content
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

Check field nullability for custom extension types #69

Merged
merged 1 commit into from
Nov 19, 2020

Conversation

quinnj
Copy link
Member

@quinnj quinnj commented Nov 19, 2020

For custom extension types (currently automatically supported for Char
and Symbol types), we were failing to take into account whether the
field was nullable or not; this led to the case where a column might be
['a', missing], but when deserializing, the column type was just
Char instead of Union{Char, Missing}. The fix is to enhance the
ArrowTypes.extensiontype function to also take the field argument
and check the nullability before returning.

Fixes #68

For custom extension types (currently automatically supported for `Char`
and `Symbol` types), we were failing to take into account whether the
field was nullable or not; this led to the case where a column might be
`['a', missing]`, but when deserializing, the column type was just
`Char` instead of `Union{Char, Missing}`. The fix is to enhance the
`ArrowTypes.extensiontype` function to also take the `field` argument
and check the nullability before returning.
@quinnj quinnj merged commit c33a818 into master Nov 19, 2020
@quinnj quinnj deleted the jq/nullableextensiontypes branch November 19, 2020 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Wrong handling of missing with Char
1 participant