[jira] [Resolved] (IMPALA-2111) Parquet TIMESTAMP is in milliseconds

["Csaba Ringhofer (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Csaba Ringhofer resolved IMPALA-2111.
-------------------------------------
    Resolution: Done

> Parquet TIMESTAMP is in milliseconds
> ------------------------------------
>
>                 Key: IMPALA-2111
>                 URL: https://issues.apache.org/jira/browse/IMPALA-2111
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.2, Impala 2.3.0
>            Reporter: Andrés Cordero
>            Priority: Minor
>              Labels: parquet, sqoop
>         Attachments: timestamp_millis.parquet
>
>
> Based on documentation:
> http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/impala_parquet.html#parquet_data_types_unique_1
> INT96 is mapping to TIMESTAMP in Impala.
> A Sqoop import from DATE, DATETIME and TIMESTAMP will map to INT64 annotated with TIMESTAMP_MILLIS (sqlType 91/93) as described in:
> https://github.com/apache/parquet-format/blob/master/LogicalTypes.md
> In Impala this appears as a BIGINT, which casting to TIMESTAMP will produce wrong results as the underlying value is in milliseconds, while the cast expects seconds.
> Impala should recognize INT64 + OriginalType DATE/DATETIME/TIMESTAMP as TIMESTAMP in milliseconds.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org