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 "Sahil Takiar (Jira)" <ji...@apache.org> on 2020/10/01 19:14:00 UTC

[jira] [Assigned] (IMPALA-3335) Allow single-node optimization with joins.

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

Sahil Takiar reassigned IMPALA-3335:
------------------------------------

    Assignee: Sahil Takiar

> Allow single-node optimization with joins.
> ------------------------------------------
>
>                 Key: IMPALA-3335
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3335
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>    Affects Versions: Impala 2.5.0
>            Reporter: Alexander Behm
>            Assignee: Sahil Takiar
>            Priority: Minor
>              Labels: ramp-up
>
> Now that IMPALA-561 has been fixed, we can remove the workaround that disables the our single-node optimization for any plan with joins. See MaxRowsProcessedVisitor.java:
> {code}
> } else if (caller instanceof HashJoinNode || caller instanceof NestedLoopJoinNode) {
>   // Revisit when multiple scan nodes can be executed in a single fragment, IMPALA-561
>   abort_ = true;
>   return;
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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