You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Carl Steinbach (JIRA)" <ji...@apache.org> on 2012/07/26 03:34:34 UTC

[jira] [Comment Edited] (HIVE-3289) sort merge join may not work silently

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

Carl Steinbach edited comment on HIVE-3289 at 7/26/12 1:32 AM:
---------------------------------------------------------------

-1

bq. I also am not a fan of hive.mapred.mode  If you turn it off, you may unintentionally turn off other checks, and it uses strict/nonstrict instead of true/false which is easier to validate. That's, at best, a problem for another JIRA, though, as it's fairly well established.

I agree with Kevin, but I don't think this should be postponed for another JIRA. Please add a new configuration property now instead of further overloading what is an already ill-defined and poorly documented configuration property.

                
      was (Author: cwsteinbach):
    -1

bq. I also am not a fan of hive.mapred.mode  If you turn it off, you may unintentionally turn off other checks, and it uses strict/nonstrict instead of true/false which is easier to validate. That's, at best, a problem for another JIRA, though, as it's fairly well established.

I agree with Kevin, but I don't think this should be postponed for another JIRA. Please add a new configuration property now instead of further overloading what is already ill-defined and poorly documented configuration property.

                  
> sort merge join may not work silently
> -------------------------------------
>
>                 Key: HIVE-3289
>                 URL: https://issues.apache.org/jira/browse/HIVE-3289
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Namit Jain
>            Assignee: Namit Jain
>
> The user does not know, if the sort-merge join is working or not.
> create table table_asc(key int, value string) CLUSTERED BY (key) SORTED BY (key asc) 
> INTO 1 BUCKETS STORED AS RCFILE; 
> create table table_desc(key int, value string) CLUSTERED BY (key) SORTED BY (key desc) 
> INTO 1 BUCKETS STORED AS RCFILE; 
> set hive.enforce.sorting = true;
> insert overwrite table table_asc select key, value from src;    
> insert overwrite table table_desc select key, value from src;
> set hive.optimize.bucketmapjoin = true;
> set hive.optimize.bucketmapjoin.sortedmerge = true;
> set hive.input.format = org.apache.hadoop.hive.ql.io.BucketizedHiveInputFormat;
> explain 
> select /*+mapjoin(a)*/ * from table_asc a join table_desc b on a.key = b.key;
> select /*+mapjoin(a)*/ * from table_asc a join table_desc b on a.key = b.key;
> explain
> select /*+mapjoin(b)*/ * from table_asc a join table_desc b on a.key = b.key;
> select /*+mapjoin(b)*/ * from table_asc a join table_desc b on a.key = b.key;
> In the above test, the sort-merge join is not obeyed as expected.
> If you user explicitly asked for sort-merge join, and it is not being
> obeyed, the operation should fail.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira