hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuefu Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16418) Allow HiveKey to skip some bytes for comparison
Date Thu, 13 Apr 2017 18:54:41 GMT

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

Xuefu Zhang commented on HIVE-16418:
------------------------------------

For datatype "TIMESTAMP WITH TIME ZONE", I don't think there is a standard on how it's represented
internally or whether the original timezone needs to be  maintained. Almost unexceptionally,
TIMESTAMP WITH TIME ZONE just means that the column can understand input time in various timezones
rather than carrying the timezone over. This is the case for Postgres, as Gopal mentioned
above.

Carrying over the original timezone, great functionality, brings implementation complexity.
The complexity comes as we are combining two values in one field: a timestamp value (either
local or UTC) and a timezone code.

Personally I'd be happy to see if Hive can carry out timezone info. (It may be worth checking
if we can extend HiveKey for timestamptz.) Given the complexity, I'd be as happy if we just
follow what Postgres does if the original problems such as those in HIVE-14305 are solved.

> Allow HiveKey to skip some bytes for comparison
> -----------------------------------------------
>
>                 Key: HIVE-16418
>                 URL: https://issues.apache.org/jira/browse/HIVE-16418
>             Project: Hive
>          Issue Type: New Feature
>            Reporter: Rui Li
>            Assignee: Rui Li
>         Attachments: HIVE-16418.1.patch
>
>
> The feature is required when we have to serialize some fields and prevent them from being
used in comparison, e.g. HIVE-14412.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message