[
https://issues.apache.org/jira/browse/DRILL-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937343#comment-15937343
]
Rahul Challapalli commented on DRILL-4373:
------------------------------------------
Thanks [~knguyen] For 3 and 4 we can use
'`store.parquet.reader.int96_as_timestamp`=true/false.' for testing. Also do
you know if we can somehow enable the configuration option in a view? (table
option?) Otherwise the end user experience will not be good as they have to
know which table is generated from hive and which from drill. By having a view
which defines how to interpret the timestamp column, then end users can be
de-coupled from this knowledge. What do you think?
> Drill and Hive have incompatible timestamp representations in parquet
> ---------------------------------------------------------------------
>
> Key: DRILL-4373
> URL: https://issues.apache.org/jira/browse/DRILL-4373
> Project: Apache Drill
> Issue Type: Improvement
> Components: Storage - Hive, Storage - Parquet
> Affects Versions: 1.8.0
> Reporter: Rahul Challapalli
> Assignee: Vitalii Diravka
> Labels: doc-impacting
> Fix For: 1.10.0
>
>
> git.commit.id.abbrev=83d460c
> I created a parquet file with a timestamp type using Drill. Now if I define a
> hive table on top of the parquet file and use "timestamp" as the column type,
> drill fails to read the hive table through the hive storage plugin
> Implementation:
> Added int96 to timestamp converter for both parquet readers and controling it
> by system / session option "store.parquet.int96_as_timestamp".
> The value of the option is false by default for the proper work of the old
> query scripts with the "convert_from TIMESTAMP_IMPALA" function.
> When the option is true using of that function is unnesessary and can lead to
> the query fail.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
