[ https://issues.apache.org/jira/browse/HIVE-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848096#comment-13848096 ]
Hive QA commented on HIVE-5973: ------------------------------- {color:green}Overall{color}: +1 all checks pass Here are the results of testing the latest attachment: https://issues.apache.org/jira/secure/attachment/12618717/HIVE-5973.2.patch {color:green}SUCCESS:{color} +1 4785 tests passed Test results: http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/637/testReport Console output: http://bigtop01.cloudera.org:8080/job/PreCommit-HIVE-Build/637/console Messages: {noformat} Executing org.apache.hive.ptest.execution.PrepPhase Executing org.apache.hive.ptest.execution.ExecutionPhase Executing org.apache.hive.ptest.execution.ReportingPhase {noformat} This message is automatically generated. ATTACHMENT ID: 12618717 > 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 > > Attachments: HIVE-5973.1.patch, HIVE-5973.2.patch > > > 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)