[
https://issues.apache.org/jira/browse/HIVE-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843946#comment-13843946
]
Vikram Dixit K commented on HIVE-5973:
--------------------------------------
It is quite easy to reproduce this on a cluster but I haven't had success
with our unit tests. I will come up with one and post it here.
Thanks
Vikram.
--
Nothing better than when appreciated for hard work.
-Mark
> SMB joins produce incorrect results with multiple partitions and buckets
> ------------------------------------------------------------------------
>
> Key: HIVE-5973
> URL: https://issues.apache.org/jira/browse/HIVE-5973
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.13.0
> Reporter: Vikram Dixit K
> Assignee: Vikram Dixit K
> Fix For: 0.13.0
>
>
> It looks like there is an issue with re-using the output object array in the
> select operator. When we read rows of the non-big tables, we hold on to the
> output object in the priority queue. This causes hive to produce incorrect
> results because all the elements in the priority queue refer to the same
> object and the join happens on only one of the buckets.
> {noformat}
> output[i] = eval[i].evaluate(row);
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
