[
https://issues.apache.org/jira/browse/TAJO-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058421#comment-14058421
]
ASF GitHub Bot commented on TAJO-927:
-------------------------------------
Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/65#issuecomment-48696287
+1
The change is straightforward and includes the unit test.
> Broadcast Join with Large, Small, Large, Small tables makes a wrong plan.
> -------------------------------------------------------------------------
>
> Key: TAJO-927
> URL: https://issues.apache.org/jira/browse/TAJO-927
> Project: Tajo
> Issue Type: Bug
> Reporter: Hyoungjun Kim
> Assignee: Hyoungjun Kim
> Priority: Minor
>
> {code:sql}
> select count(*) from large1
> inner join small1 on large1_id = small1_id
> left outer join large2 on large1_id = large2_id
> left outer join small2 on large1_id = small2_id
> {code}
> Current tajo planner makes the plan as following. All large tables(large1,
> large2) are scanned in a single execution block. Each table should have a
> execution block.
> {noformat}
> |-eb_1404871198908_0000_000005
> |-eb_1404871198908_0000_000004
> |-eb_1404871198908_0000_000003
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
