[
https://issues.apache.org/jira/browse/PARQUET-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174447#comment-17174447
]
Tamas Palfy commented on PARQUET-1793:
--------------------------------------
[~kings129], I think this idea was deemed not to be pursued in the end.
The original reason was that Hive can (could?) only read INT96 formatted
timestamps from Parquet.
However INT96 is deprecated and ultimately Hive should support INT64 timestamp
_when dealing with parquet_. (Can already read INT64 timestamp from Avro for
example).
I'm not sure where Hive is on this issue though. It's possible that it can do
it already, but it's also possible that the works have been postponed
indefinitely.
> Support writing INT96 timestamp from avro
> -----------------------------------------
>
> Key: PARQUET-1793
> URL: https://issues.apache.org/jira/browse/PARQUET-1793
> Project: Parquet
> Issue Type: Improvement
> Reporter: Tamas Palfy
> Priority: Major
>
> Add support for writing avro LONG/timestamp-millis data in INT96 (or int the
> current INT64) format in parquet.
> Add a config flag to select the required timestamp output format (INT96 or
> INT64).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
