hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikram Dixit K (JIRA)" <>
Subject [jira] [Updated] (HIVE-3403) user should not specify mapjoin to perform sort-merge bucketed join
Date Wed, 13 Feb 2013 00:41:15 GMT


Vikram Dixit K updated HIVE-3403:

    Attachment: auto_sortmerge_join_1_modified.q

I run with a modified version of the auto_sortmerge_join_1.q file (attached to the JIRA) and
create a query where 2 of the tables in a join are sorted and bucketed and the 3rd table is
not sorted. I have enabled the auto map join convert config. I am seeing this exception:

FAILED: ClassCastException org.apache.hadoop.hive.ql.exec.SMBMapJ
oinOperator cannot be cast to org.apache.hadoop.hive.ql.exec.MapJoinOperator

I do not see the exception if I set the noConditionalTask.size to a size greater than the
size of the 2 small tables (src1 and small_table) for e.g. 500.
> 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: auto_sortmerge_join_1_modified.q, 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.23.patch, hive.3403.24.patch, hive.3403.25.patch, hive.3403.26.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