[
https://issues.apache.org/jira/browse/PARQUET-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610663#comment-14610663
]
Ryan Blue commented on PARQUET-323:
-----------------------------------
While we don't want to encourage anyone to use int96 as a timestamp, I'm not
sure if it is necessary to get rid of the type entirely. If int96 is a JVM and
hardware-supported type, then it makes sense to keep it. But if everything
jumps to int128 instead, then maybe we should go with that instead. Do we have
enough information to make that decision yet?
> 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)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
