[
https://issues.apache.org/jira/browse/TAJO-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164654#comment-14164654
]
Hudson commented on TAJO-1107:
------------------------------
SUCCESS: Integrated in Tajo-master-build #406 (See
[https://builds.apache.org/job/Tajo-master-build/406/])
TAJO-1107: Broadcast join on non-leaf node scans only first data file.
(babokim: rev 5f64cbb1a64e2bcc034fb3f82c65ae448cb824bd)
*
tajo-core/src/test/resources/results/TestJoinBroadcast/testMultiplePartitionedBroadcastDataFileWithZeroLength2.result
*
tajo-core/src/test/resources/results/TestJoinBroadcast/testMultiplePartitionedBroadcastDataFileWithZeroLength.result
*
tajo-core/src/test/resources/results/TestJoinBroadcast/testMultipleBroadcastDataFileWithZeroLength2.result
* tajo-core/src/main/java/org/apache/tajo/master/querymaster/Repartitioner.java
*
tajo-core/src/test/resources/queries/TestJoinBroadcast/testMultiplePartitionedBroadcastDataFileWithZeroLength.sql
*
tajo-core/src/test/resources/queries/TestJoinBroadcast/testMultipleBroadcastDataFileWithZeroLength2.sql
* tajo-core/src/test/java/org/apache/tajo/engine/query/TestJoinBroadcast.java
*
tajo-core/src/test/resources/queries/TestJoinBroadcast/testMultiplePartitionedBroadcastDataFileWithZeroLength2.sql
* CHANGES
> 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)
