spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Spark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-20366) Fix recursive join reordering: inside joins are not reordered
Date Tue, 18 Apr 2017 07:30:41 GMT

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

Apache Spark commented on SPARK-20366:
--------------------------------------

User 'wzhfy' has created a pull request for this issue:
https://github.com/apache/spark/pull/17668

> Fix recursive join reordering: inside joins are not reordered
> -------------------------------------------------------------
>
>                 Key: SPARK-20366
>                 URL: https://issues.apache.org/jira/browse/SPARK-20366
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 2.2.0
>            Reporter: Zhenhua Wang
>
> If a plan has multi-level successive joins, e.g.:
> ```
>          Join
>          /     \
>      Union  t5
>       /    \
>     Join t4
>     /    \
>   Join t3
>   /  \
>  t1  t2
> ```
> Currently we fail to reorder the inside joins, i.e. t1, t2, t3.
> In join reorder, we use `OrderedJoin` to indicate a join has been ordered, such that
when transforming down the plan, these joins don't need to be rerodered again.
> But there's a problem in the definition of `OrderedJoin`:
> The real join node is a parameter, rather than a child. This breaks the transform procedure
because `mapChildren` applies transform on parameters which should be children.



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

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


Mime
View raw message