[ 
https://issues.apache.org/jira/browse/DRILL-8109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479347#comment-17479347
 ] 

ASF GitHub Bot commented on DRILL-8109:
---------------------------------------

cdmikechen edited a comment on pull request #2431:
URL: https://github.com/apache/drill/pull/2431#issuecomment-1017483944


   @vvysotskyi  
   Hi~ `org.apache.hadoop.io.LongWritable` is in `hadoop-common` package, and 
it is used from hive1. it can build with hive2 and hive3.
   You should be talking about 
`org.apache.hadoop.hive.serde2.io.TimestampWritableV2`, it is used from hive3.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


> Drill can not read parquet timestamp type with logical type in hive storage 
> plugin
> ----------------------------------------------------------------------------------
>
>                 Key: DRILL-8109
>                 URL: https://issues.apache.org/jira/browse/DRILL-8109
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - Hive
>    Affects Versions: 1.19.0
>         Environment: drill 1.19.0 
> hive 3.12
>            Reporter: cdmikechen
>            Priority: Major
>             Fix For: 1.20.0
>
>
> Parquet timestamp int96 had been deprecated.
> https://github.com/apache/parquet-format/pull/86/files
> Many computing engines that support parquet reading (such as Hive4, Hudi, 
> Spark and so on) can use Int64 as the time storage type. When using these 
> computing engines to read parquet files, we should also support long data 
> type reading.
> We should support int64 with logical type timestamp by hive storage.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to