[
https://issues.apache.org/jira/browse/TAJO-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163598#comment-14163598
]
ASF GitHub Bot commented on TAJO-1107:
--------------------------------------
GitHub user babokim opened a pull request:
https://github.com/apache/tajo/pull/193
TAJO-1107: Broadcast join on non-leaf node scans only first data file.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/babokim/tajo TAJO-1107
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/193.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #193
----
commit 04d7b8537a69752fb62b9c2d83cade77124c8a9d
Author: HyoungJun Kim <[email protected]>
Date: 2014-10-08T08:47:00Z
TAJO-1107: Broadcast join on non-leaf node scans only first data file.
commit 4ccc1bdab28acb9796035b7723f4bc53ff732e48
Author: HyoungJun Kim <[email protected]>
Date: 2014-10-08T08:47:47Z
Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/tajo
commit 8cc4aa3248d6a6e81c328cc53844ae1eb7290cf5
Author: HyoungJun Kim <[email protected]>
Date: 2014-10-08T14:24:42Z
Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/tajo into
TAJO-1107
----
> Broadcast join on non-leaf node scans only first data file.
> -----------------------------------------------------------
>
> Key: TAJO-1107
> URL: https://issues.apache.org/jira/browse/TAJO-1107
> Project: Tajo
> Issue Type: Bug
> Reporter: Hyoungjun Kim
> Assignee: Hyoungjun Kim
> Priority: Minor
>
> Fragments are determined by the Repartitioner. In the case of broadcast join
> Repartitioner uses different determine login according to node type(lead,
> non-leaf).
> Currently Tajo only uses first data file when broadcast join is non-leaf
> node. This is the cause of incorrect results.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
