You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Songzhi Liu (JIRA)" <ji...@apache.org> on 2019/06/25 19:01:00 UTC
[jira] [Commented] (PARQUET-323) INT96 should be marked as
deprecated
[ https://issues.apache.org/jira/browse/PARQUET-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872626#comment-16872626 ]
Songzhi Liu commented on PARQUET-323:
-------------------------------------
[~lv] Hi Lars, is it the direction of the community to deprecate INT96 support? In that case, what will be used to support nanosec precision? In some financial services use cases, support for nanosecond precision is critical. Could you please advise the potential plan of the deprecation plan?
> 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
> Assignee: Lars Volker
> Priority: Major
> Fix For: format-2.5.0
>
>
> 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
(v7.6.3#76005)