[
https://issues.apache.org/jira/browse/ARROW-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881495#comment-16881495
]
Joris Van den Bossche commented on ARROW-5889:
----------------------------------------------
This is very much related to ARROW-5878 /
https://github.com/apache/arrow/pull/4825, but then for the other way around.
With the introduction of LogicalTypes, the old ConvertedTypes
TIMESTAMP_MICROS/MILLIS are now interpreted as always {{isAdjustedToUTC}}.
Reverting this corresponds to the second bullet point that Wes mentioned on the
other PR at https://github.com/apache/arrow/pull/4825#issuecomment-509388706
> [Python][C++] Parquet backwards compat for timestamps without timezone broken
> -----------------------------------------------------------------------------
>
> Key: ARROW-5889
> URL: https://issues.apache.org/jira/browse/ARROW-5889
> Project: Apache Arrow
> Issue Type: Bug
> Affects Versions: 0.14.0
> Reporter: Florian Jetter
> Priority: Minor
> Fix For: 0.14.1
>
> Attachments: 0.12.1.parquet, 0.13.0.parquet
>
>
> When reading a parquet file which has timestamp fields they are read as a
> timestamp with timezone UTC if the parquet file was written by pyarrow 0.13.0
> and/or 0.12.1.
> Expected behavior would be that they are loaded as timestamps without any
> timezone information.
> The attached files contain one row for all basic types and a few nested
> types, the timestamp fields are called datetime64 and datetime64_tz
> see also
> [https://github.com/JDASoftwareGroup/kartothek/tree/master/reference-data/arrow-compat]
> [https://github.com/JDASoftwareGroup/kartothek/blob/c47e52116e2dc726a74d7d6b97922a0252722ed0/tests/serialization/test_arrow_compat.py#L31]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
