[
https://issues.apache.org/jira/browse/HIVE-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715797#comment-13715797
]
Brock Noland commented on HIVE-4611:
------------------------------------
It's in the console output:
https://builds.apache.org/job/PreCommit-HIVE-Build/88/console
{noformat}
2013-07-19 03:05:39,295 WARN PTest.run:163 6 failed tests
2013-07-19 03:05:39,295 WARN PTest.run:166
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_join2
2013-07-19 03:05:39,295 WARN PTest.run:166
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_smb_bucketmapjoin
2013-07-19 03:05:39,295 WARN PTest.run:166
org.apache.hadoop.hive.cli.TestMinimrCliDriver.testCliDriver_bucketmapjoin6
2013-07-19 03:05:39,295 WARN PTest.run:166
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_auto_sortmerge_join_1
2013-07-19 03:05:39,296 WARN PTest.run:166
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_auto_sortmerge_join_15
2013-07-19 03:05:39,296 WARN PTest.run:166
org.apache.hadoop.hive.ql.TestErrorMsg.testUniqueErrorCode
{noformat}
> SMB joins fail based on bigtable selection policy.
> --------------------------------------------------
>
> Key: HIVE-4611
> URL: https://issues.apache.org/jira/browse/HIVE-4611
> Project: Hive
> Issue Type: Bug
> Components: Query Processor
> Affects Versions: 0.11.0
> Reporter: Vikram Dixit K
> Assignee: Vikram Dixit K
> Fix For: 0.11.1
>
> Attachments: HIVE-4611.2.patch, HIVE-4611.3.patch, HIVE-4611.4.patch,
> HIVE-4611.patch
>
>
> The default setting for
> hive.auto.convert.sortmerge.join.bigtable.selection.policy will choose the
> big table as the one with largest average partition size. However, this can
> result in a query failing because this policy conflicts with the big table
> candidates chosen for outer joins. This policy should just be a tie breaker
> and not have the ultimate say in the choice of tables.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
