hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Namit Jain (JIRA)" <>
Subject [jira] [Commented] (HIVE-3403) user should not specify mapjoin to perform sort-merge bucketed join
Date Thu, 31 Jan 2013 07:01:17 GMT


Namit Jain commented on HIVE-3403:

To help	in review, the class hierarchy is:


The context needed is:


Most of the code in AbstractBucketJoinProc and AbstractSMBJoinProc is old code moved.
BucketMapjoinOptProc is also old code – but there has been little refactoring to break it
up into context.

As such, the only new code is SortedMergeJoinProc. Due to the refactoring, I am	able to	re-use
a lot of	code
between	map-join and join processing.

> user should not specify mapjoin to perform sort-merge bucketed join
> -------------------------------------------------------------------
>                 Key: HIVE-3403
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Namit Jain
>            Assignee: Namit Jain
>         Attachments: hive.3403.10.patch, hive.3403.11.patch, hive.3403.12.patch, hive.3403.13.patch,
hive.3403.14.patch, hive.3403.15.patch, hive.3403.16.patch, hive.3403.17.patch, hive.3403.18.patch,
hive.3403.19.patch, hive.3403.1.patch, hive.3403.21.patch, hive.3403.22.patch, hive.3403.2.patch,
hive.3403.3.patch, hive.3403.4.patch, hive.3403.5.patch, hive.3403.6.patch, hive.3403.7.patch,
hive.3403.8.patch, hive.3403.9.patch
> Currently, in order to perform a sort merge bucketed join, the user needs
> to set hive.optimize.bucketmapjoin.sortedmerge to true, and also specify the 
> mapjoin hint.
> The user should not specify any hints.

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:

View raw message