[
https://issues.apache.org/jira/browse/HIVE-22224?focusedWorklogId=757536&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-757536
]
ASF GitHub Bot logged work on HIVE-22224:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Apr/22 00:18
Start Date: 16/Apr/22 00:18
Worklog Time Spent: 10m
Work Description: github-actions[bot] closed pull request #3002: WIP:
HIVE-22224 support long as timestamp
URL: https://github.com/apache/hive/pull/3002
Issue Time Tracking
-------------------
Worklog Id: (was: 757536)
Time Spent: 1h (was: 50m)
> Support Parquet-Avro Timestamp Type
> -----------------------------------
>
> Key: HIVE-22224
> URL: https://issues.apache.org/jira/browse/HIVE-22224
> Project: Hive
> Issue Type: Bug
> Components: Database/Schema
> Affects Versions: 2.3.5, 2.3.6
> Reporter: cdmikechen
> Assignee: cdmikechen
> Priority: Major
> Labels: parquet, pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When user create an external table and import a parquet-avro data with 1.8.2
> version which supported logical_type in Hive2.3 or before version, Hive can
> not read timestamp type column data correctly.
> Hive will read it as LongWritable which it actually stores as
> long(logical_type=timestamp-millis).So we may add some codes in
> org.apache.hadoop.hive.serde2.objectinspector.primitive.WritableTimestampObjectInspector.java
> to let Hive cast long type to timestamp type.
> Some code like below:
>
> public Timestamp getPrimitiveJavaObject(Object o) {
> if (o instanceof LongWritable) {
> return new Timestamp(((LongWritable) o).get());
> }
> return o == null ? null : ((TimestampWritable) o).getTimestamp();
> }
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
