ENH: fix arrow roundtrip for ExtensionDtypes in absence of pandas metadata #34275
Conversation
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
TomAugspurger
approved these changes
May 20, 2020
|
lgtm. do we need a whatsnew note? |
|
A whatsnew note for it might be a bit "obscure", but can certainly add one if preferred |
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.
An oversight in our Arrow Extension Types for period and interval to also define the conversion to the equivalent pandas dtype. This ensures that the arrow->pandas conversion also works if there is no "pandas_metadata" in the schema's metadata, eg when this metadata was lost during some operations (up to now, the pandas ExtensionDtype was reconstructed based on the string name in the stored metadata).
See https://arrow.apache.org/docs/python/extending_types.html#conversion-to-pandas