[
https://issues.apache.org/jira/browse/IMPALA-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Jacobs resolved IMPALA-4825.
------------------------------------
Resolution: Not A Problem
Fix Version/s: Impala 2.9.0
Kudu isn't going to have a 12byte timestamp as this JIRA states, they will only
have a 64-bit unix time in micros.
> 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)
