[BUG] Fix parquet timestamp tz roundtrip inference #1625
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.
This required a fix in our arrow2 fork: Eventual-Inc/arrow2@3a23c78
Essentially when Parquet has a type that is "timezone aware", Arrow2 will always infer it as
"+00:00"
(notNone
as previously assumed). However if the embedded Arrow schema on the Parquet file tells us that the timezone should actually be something else, we need to override"+00:00"
with the one provided by the embedded Arrow schema.