[
https://issues.apache.org/jira/browse/PARQUET-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795001#comment-16795001
]
Nandor Kollar commented on PARQUET-1545:
----------------------------------------
[~swast] actually Parquet already supports both timezone-naive and
timezone-aware timestamps too. The logical type API is improved in 1.11.0
(based on the recent improvement in parquet-format), and the timestamp logical
type introduced an additional {{isAdjustedToUTC}} parameter, which tells what
is the semantic of the given timestamp field: {{false}} means timezone-naive,
and {{true}} means timezone-aware timestamp.
> 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)
