You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2019/05/15 22:42:00 UTC

[jira] [Updated] (IMPALA-4233) Revisit handling of expr codegen failures

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

Tim Armstrong updated IMPALA-4233:
----------------------------------
    Summary: Revisit handling of expr codegen failures  (was: Revisit handling of codegen failed)

> Revisit handling of expr codegen failures
> -----------------------------------------
>
>                 Key: IMPALA-4233
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4233
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 2.8.0
>            Reporter: bharath v
>            Assignee: Michael Ho
>            Priority: Minor
>              Labels: codegen
>
> FragmentInstanceState::Open() can fail if codegen of expressions fails:
> {code}
>       // It shouldn't be fatal to fail codegen. However, until IMPALA-4233 is fixed,
>       // ScalarFnCall has no fall back to interpretation when codegen fails so propagates
>       // the error status for now.
>       RETURN_IF_ERROR(runtime_state_->CodegenScalarFns());
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org