You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Xuefu Zhang (Jira)" <ji...@apache.org> on 2020/07/21 18:00:00 UTC
[jira] [Commented] (HIVE-19853) Arrow serializer needs to create a
TimeStampMicroTZVector instead of TimeStampMicroVector
[ https://issues.apache.org/jira/browse/HIVE-19853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162227#comment-17162227 ]
Xuefu Zhang commented on HIVE-19853:
------------------------------------
Hi [~teddy.choi] and [~ewohlstadter],
I understand this is an old JIRA, but I'm wondering what the reason is for serializing Hive's timestamp, which is timezoneless according to the doc, to UTC in Arrow serializer. The JIRA mentioned about Spark, but I don't fully understand how Spark decided our choice.
I asked about this because I was trying to integrate Hive with a PG-like system, where timestamp without time zone expects values (in Arrow format) without any timezone specification, which created a headache for me.
Any input to this would be greatly appreciated. Thanks.
> Arrow serializer needs to create a TimeStampMicroTZVector instead of TimeStampMicroVector
> -----------------------------------------------------------------------------------------
>
> Key: HIVE-19853
> URL: https://issues.apache.org/jira/browse/HIVE-19853
> Project: Hive
> Issue Type: Bug
> Reporter: Teddy Choi
> Assignee: Teddy Choi
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.1.0, 4.0.0
>
> Attachments: HIVE-19853.1.patch, HIVE-19853.2.patch, HIVE-19853.3.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> HIVE-19723 changed nanosecond to microsecond in Arrow serialization. However, it needs to be microsecond with time zone.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)