impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Jacobs (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IMPALA-5595) Impala shouldn't set KuduScanner timestamp feature flag unless necessary
Date Thu, 29 Jun 2017 14:40:00 GMT

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

Matthew Jacobs resolved IMPALA-5595.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.10.0

7e4f23507197b1a9e5b10b65e85dcef064bf7070

> Impala shouldn't set KuduScanner timestamp feature flag unless necessary
> ------------------------------------------------------------------------
>
>                 Key: IMPALA-5595
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5595
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.9.0
>            Reporter: Matthew Jacobs
>            Assignee: Matthew Jacobs
>              Labels: kudu
>             Fix For: Impala 2.10.0
>
>
> To support Kudu timestamps, Impala sets a KuduScanner flag which pads the result tuples:
 KuduScanner::PAD_UNIXTIME_MICROS_TO_16_BYTES
> It is always set, which is correct, but means that newer versions of Impala cannot scan
older Kudus even if there are no TIMESTAMP columns.
> The flag should just be set when there are TIMESTAMP columns.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message