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

Carl Steinbach commented on HIVE-3171:
--------------------------------------

@Namit: The Apache Hive Project Bylaws are located here: 
https://cwiki.apache.org/confluence/display/Hive/Bylaws

The bylaws explicitly prohibit committers from voting on their own patches, but 
they don't prohibit committers from committing their own patches as long as 
another committer has already reviewed and +1'd the patch. It's also worth 
noting that the bylaws stipulate that the +1 vote must be sent to dev@hive, and 
that 24 hours must elapse between the first +1 vote and the point at which the 
patch is committed.
                
> Bucketed sort merge join doesn't work when multiple files exist for small 
> alias
> -------------------------------------------------------------------------------
>
>                 Key: HIVE-3171
>                 URL: https://issues.apache.org/jira/browse/HIVE-3171
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.10.0
>            Reporter: Joey Echeverria
>            Assignee: Navis
>              Labels: bucketing, joins, partitioning
>         Attachments: HIVE-3171.1.patch.txt
>
>
> Executing a query with the MAPJOIN hint and the bucketed sort merge join 
> optimizations enabled:
> {noformat}
> set hive.input.format=org.apache.hadoop.hive.ql.io.BucketizedHiveInputFormat;
> set hive.optimize.bucketmapjoin = true;
> set hive.optimize.bucketmapjoin.sortedmerge = true;
> {noformat}
> works fine with partitioned tables if there is only one partition in the 
> table. However, if you add a second partition, Hive attempts to do a regular 
> map-side join which can fail because the tables are too large. Hive ought to 
> be able to still do the bucketed sort merge join with partitions.

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

Reply via email to