[
https://issues.apache.org/jira/browse/PARQUET-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902218#comment-15902218
]
Lars Volker commented on PARQUET-323:
-------------------------------------
We discussed this issue in today's Parquet sync and agreed to deprecate INT96.
As a replacement to store timestamps (the most common use for INT96) we will
encourage all projects who currently use INT96 to switch to INT64 and either
use the TIMESTAMP_MILLIS or TIMESTAMP_MICROS logical types.
We will not fix the ordering issues around INT96 that resulted in parquet-mr
writing wrong min/max statistics.
> INT96 should be marked as deprecated
> ------------------------------------
>
> Key: PARQUET-323
> URL: https://issues.apache.org/jira/browse/PARQUET-323
> Project: Parquet
> Issue Type: Bug
> Components: parquet-format
> Reporter: Cheng Lian
>
> As discussed in the mailing list, {{INT96}} is only used to represent nanosec
> timestamp in Impala for some historical reasons, and should be deprecated.
> Since nanosec precision is rarely a real requirement, one possible and simple
> solution would be replacing {{INT96}} with {{INT64 (TIMESTAMP_MILLIS)}} or
> {{INT64 (TIMESTAMP_MICROS)}}.
> Several projects (Impala, Hive, Spark, ...) support INT96.
> We need a clear spec of the replacement and the path to deprecation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
