hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Namit Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-3403) user should not specify mapjoin to perform sort-merge bucketed join
Date Thu, 20 Sep 2012 11:17:07 GMT

    [ https://issues.apache.org/jira/browse/HIVE-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459517#comment-13459517
] 

Namit Jain commented on HIVE-3403:
----------------------------------

[~navis], thinking more about it - I am not sure.
If we go the route of hive.auto.convert.join, do we risk deployment ?
I mean, hive.auto.convert.join is a very stable feature and should be set to true
in most of the installations. Do we want to risk a new functionality on this one ?

I would say - let us have an additional config. for now, but once we are more confident of
it's functionality, we can add this behavior in hive.auto.convert.join.
                
> user should not specify mapjoin to perform sort-merge bucketed join
> -------------------------------------------------------------------
>
>                 Key: HIVE-3403
>                 URL: https://issues.apache.org/jira/browse/HIVE-3403
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Namit Jain
>            Assignee: Namit Jain
>         Attachments: hive.3403.1.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: http://www.atlassian.com/software/jira

Mime
View raw message