impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Knupp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IMPALA-4825) Change Timestamp representation for binary compatibility with Kudu.
Date Fri, 12 May 2017 00:06:04 GMT

     [ https://issues.apache.org/jira/browse/IMPALA-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Knupp resolved IMPALA-4825.
---------------------------------
    Resolution: Won't Do

> Change Timestamp representation for binary compatibility with Kudu.
> -------------------------------------------------------------------
>
>                 Key: IMPALA-4825
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4825
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 2.8.0
>            Reporter: Alexander Behm
>            Assignee: Matthew Jacobs
>            Priority: Critical
>              Labels: kudu, performance
>             Fix For: Impala 2.9.0
>
>
> Kudu represents a timestamp as a 12-byte field in rows returned to Impala. In addition,
Kudu stores the 4-byte date portion first, followed by the 8-byte time portion. Impala has
those fields reversed (timestamp-value.h) and treats a timestamp as a 16-byte field.
> In order to maintain Impala/Kudu tuple-format compatibility, we should change Impala's
representation to match Kudu's.



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

Mime
View raw message