[
https://issues.apache.org/jira/browse/TAJO-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163998#comment-14163998
]
ASF GitHub Bot commented on TAJO-1107:
--------------------------------------
Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/193#issuecomment-58410665
+1
The patch looks good to me. The patch exactly fixes the bug and includes
enough unit tests for all cases. I leave one trivial comment. Before committing
it, please reflect the comment if you accept.
Thanks,
Hyunsik
> 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
> Fix For: 0.9.0
>
>
> 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)
