impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Armstrong (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IMPALA-391) Expr-test does not actually test the codegen path
Date Tue, 13 Jun 2017 15:14:00 GMT

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

Tim Armstrong resolved IMPALA-391.
----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.9.0

Fixed with this commit

    IMPALA-4705, IMPALA-4779, IMPALA-4780: Fix some Expr bugs with codegen
    
    This change fixes expr-test.cc to work with codegen as it's
    originally intended. Fixing it uncovers a couple of bugs fixed
    in this patch:
...
    Change-Id: I40fdb035a565ae2f9c9fbf4db48a548653ef7608
    Reviewed-on: http://gerrit.cloudera.org:8080/5732
    Reviewed-by: Michael Ho <kwho@cloudera.com>
    Tested-by: Impala Public Jenkins



> Expr-test does not actually test the codegen path
> -------------------------------------------------
>
>                 Key: IMPALA-391
>                 URL: https://issues.apache.org/jira/browse/IMPALA-391
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 1.0
>            Reporter: Nong Li
>            Assignee: Michael Ho
>            Priority: Minor
>             Fix For: Impala 2.9.0
>
>
> Expr-test only tests the codegen but not running the jitted function.



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

Mime
View raw message