[ 
https://issues.apache.org/jira/browse/IMPALA-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16838928#comment-16838928
 ] 

Bikramjeet Vig commented on IMPALA-6626:
----------------------------------------

Since the expression that fails BE evaluation during Planning phase will also 
run into the same error during execution, the ideal test case for this can be 
wrapping that kind of expression in a case statement query wherein this case 
would never be encountered.

> Failure to assign dictionary predicates should not result in query failure - 
> testing needed
> -------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-6626
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6626
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>    Affects Versions: Impala 2.9.0, Impala 2.10.0, Impala 2.11.0
>            Reporter: Alexander Behm
>            Priority: Major
>
> Assigning dictionary predicates to Parquet scans may involve evaluation of 
> expressions in the BE which could fail for various reasons. Such failures 
> should lead to non-assignment of dictionary predicates but not to query 
> failure.
> See HdfsScanNode:
> {code}
> private void addDictionaryFilter(...) {
> ...
>     try {
>       if (analyzer.isTrueWithNullSlots(conjunct)) return;
>     } catch (InternalException e) { <--- does not handle Exception which will 
> cause query to fail
>       // Expr evaluation failed in the backend. Skip this conjunct since we 
> cannot
>       // determine whether it is safe to apply it against a dictionary.
>       LOG.warn("Skipping dictionary filter because backend evaluation failed: 
> "
>           + conjunct.toSql(), e);
>       return;
>     }
> }
> {code}



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to