You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Thomas Tauber-Marshall (JIRA)" <ji...@apache.org> on 2017/04/13 21:56:41 UTC

[jira] [Resolved] (IMPALA-5206) NPE when "optimized" expression contains an aggregation

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

Thomas Tauber-Marshall resolved IMPALA-5206.
--------------------------------------------
    Resolution: Duplicate

Duplicate of IMPALA-5125

> NPE when "optimized" expression contains an aggregation
> -------------------------------------------------------
>
>                 Key: IMPALA-5206
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5206
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 2.9.0
>            Reporter: Michael Brown
>            Assignee: Thomas Tauber-Marshall
>            Priority: Critical
>              Labels: query_generator
>
> This seems similar to IMPALA-5125, but in this bug, we hit a Java NPE and error, not a DCHECK, so I think it's important to file this separately for now, since some path is different.
> query:
> {noformat}
> EXPLAIN
> SELECT IF(false, AVG(id), -1)
> FROM functional.alltypestiny;
> {noformat}
> {noformat}
> I0413 14:32:19.962172  9649 jni-util.cc:176] java.lang.NullPointerException
>         at org.apache.impala.analysis.Analyzer.getEquivClasses(Analyzer.java:1781)
>         at org.apache.impala.analysis.Analyzer.createEquivConjuncts(Analyzer.java:1744)
>         at org.apache.impala.planner.AggregationNode.init(AggregationNode.java:147)
>         at org.apache.impala.planner.SingleNodePlanner.createAggregationPlan(SingleNodePlanner.java:892)
>         at org.apache.impala.planner.SingleNodePlanner.createSelectPlan(SingleNodePlanner.java:616)
>         at org.apache.impala.planner.SingleNodePlanner.createQueryPlan(SingleNodePlanner.java:254)
>         at org.apache.impala.planner.SingleNodePlanner.createSingleNodePlan(SingleNodePlanner.java:147)
>         at org.apache.impala.planner.Planner.createPlan(Planner.java:87)
>         at org.apache.impala.service.Frontend.createExecRequest(Frontend.java:1012)
>         at org.apache.impala.service.Frontend.createExecRequest(Frontend.java:1103)
>         at org.apache.impala.service.JniFrontend.createExecRequest(JniFrontend.java:155)
> {noformat}
> Just like with IMPALA-5125, using {{set enable_expr_rewrites=false}} is a workaround. Just like with IMPALA-5125, including {{GROUP BY}} looks OK.
> [~twmarshall] can you take the first look? I'm going under the assumption that this is a dupe of IMPALA-5125 based on RCA, or at least meta-similar. Again, though, different effect (no crash) means at least initially a separate bug. Thanks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)