You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Edward Capriolo (JIRA)" <ji...@apache.org> on 2012/07/06 16:15:35 UTC

[jira] [Resolved] (HIVE-3237) hive.enforce.bucketing option seemed not working on test platform

     [ https://issues.apache.org/jira/browse/HIVE-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edward Capriolo resolved HIVE-3237.
-----------------------------------

    Resolution: Duplicate
    
> hive.enforce.bucketing option seemed not working on test platform
> -----------------------------------------------------------------
>
>                 Key: HIVE-3237
>                 URL: https://issues.apache.org/jira/browse/HIVE-3237
>             Project: Hive
>          Issue Type: Bug
>          Components: Testing Infrastructure
>    Affects Versions: 0.10.0
>            Reporter: Navis
>
> {noformat}
> create table hive_test_smb_bucket1 (key int, value string) partitioned by (ds string) clustered by (key) sorted by (key) into 2 buckets;
> create table hive_test_smb_bucket2 (key int, value string) partitioned by (ds string) clustered by (key) sorted by (key) into 4 buckets;
> set hive.enforce.bucketing = true;
> set hive.enforce.sorting = true;
> insert overwrite table hive_test_smb_bucket1 partition (ds='2010-10-15') select key, value from src;
> insert overwrite table hive_test_smb_bucket2 partition (ds='2010-10-15') select key, value from src;
> set hive.optimize.bucketmapjoin = true;
> explain extended
> SELECT /* + MAPJOIN(b) */ * FROM hive_test_smb_bucket1 a JOIN hive_test_smb_bucket2 b ON a.key = b.key;
> {noformat}
> in hive console, bucket context is shown correctly
> {noformat}
> b {000000_0=[000000_0, 000002_0], 000001_0=[000001_0, 000003_0]}
> {noformat}
> But in test platform, only one bucket is shown
> {noformat}
> b {000000_0=[000000_0]}
> {noformat}
> This prevents writing test cases for BMJoin/SMBJoin. 

--
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