You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Nandor Kollar (JIRA)" <ji...@apache.org> on 2019/03/20 10:02:01 UTC
[jira] [Resolved] (PARQUET-1545) Logical Type for timezone-naive
timestamps
[ https://issues.apache.org/jira/browse/PARQUET-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nandor Kollar resolved PARQUET-1545.
------------------------------------
Resolution: Fixed
> Logical Type for timezone-naive timestamps
> ------------------------------------------
>
> Key: PARQUET-1545
> URL: https://issues.apache.org/jira/browse/PARQUET-1545
> Project: Parquet
> Issue Type: New Feature
> Reporter: Tim Swast`
> Priority: Major
>
> {{In many systems there is a difference between a timezone-naive timestamp column (called DATETIME in BigQuery, 'logicalType': 'datetime' in Avro) and a timezone-aware timestamp (called TIMESTAMP in BigQuery and always stored in UTC). It seems from [this discussion|https://github.com/apache/parquet-format/pull/51#discussion_r119911623] and the [list of logical types|https://github.com/apache/parquet-format/blob/master/LogicalTypes.md] that parquet only has the timezone-aware version, as all timestamps are stored according to UTC.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)