You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Julien Le Dem (JIRA)" <ji...@apache.org> on 2017/03/06 19:00:33 UTC
[jira] [Updated] (PARQUET-323) INT96 should be marked as deprecated
[ https://issues.apache.org/jira/browse/PARQUET-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julien Le Dem updated PARQUET-323:
----------------------------------
Description:
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.
was: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)}}.
> 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)