[ https://issues.apache.org/jira/browse/DRILL-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937318#comment-15937318 ]
Krystal commented on DRILL-4373: -------------------------------- [~rkins] For #1, I will check. For #2, I tested that and it works as expected. For #3 and #4, TIMESTAMP_IMPALA_LOCALTIMEZONE function is removed as part of DRILL-5034. > 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)