[
https://issues.apache.org/jira/browse/HIVE-18323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329266#comment-16329266
]
Aihua Xu commented on HIVE-18323:
---------------------------------
Yeah. Right now we can't write timestamp as INT64 from hive. [~spena] Do we
need to support reading INT64 since other components can write INT64 timestamp?
> Vectorization: add the support of timestamp in
> VectorizedPrimitiveColumnReader for parquet
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-18323
> URL: https://issues.apache.org/jira/browse/HIVE-18323
> Project: Hive
> Issue Type: Sub-task
> Components: Vectorization
> Affects Versions: 3.0.0
> Reporter: Aihua Xu
> Assignee: Vihang Karajgaonkar
> Priority: Major
> Attachments: HIVE-18323.02.patch, HIVE-18323.03.patch,
> HIVE-18323.04.patch, HIVE-18323.05.patch, HIVE-18323.06.patch,
> HIVE-18323.07.patch, HIVE-18323.1.patch
>
>
> {noformat}
> CREATE TABLE `t1`(
> `ts` timestamp,
> `s1` string)
> STORED AS PARQUET;
> set hive.vectorized.execution.enabled=true;
> SELECT * from t1 SORT BY s1;
> {noformat}
> This query will throw exception since timestamp is not supported here yet.
> {noformat}
> Caused by: java.io.IOException: java.io.IOException: Unsupported type:
> optional int96 ts
> at
> org.apache.hadoop.hive.io.HiveIOExceptionHandlerChain.handleRecordReaderNextException(HiveIOExceptionHandlerChain.java:121)
> at
> org.apache.hadoop.hive.io.HiveIOExceptionHandlerUtil.handleRecordReaderNextException(HiveIOExceptionHandlerUtil.java:77)
> at
> org.apache.hadoop.hive.ql.io.HiveContextAwareRecordReader.doNext(HiveContextAwareRecordReader.java:365)
> at
> org.apache.hadoop.hive.ql.io.CombineHiveRecordReader.doNext(CombineHiveRecordReader.java:116)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
