You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/01/09 11:27:40 UTC

[jira] [Commented] (HIVE-3210) Support Bucketed mapjoin on partitioned table which has two or more partitions

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

Hudson commented on HIVE-3210:
------------------------------

Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
    HIVE-3210 Support Bucketed mapjoin on partitioned table which has two or more partitions
(Navis via namit) (Revision 1362391)

     Result = ABORTED
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1362391
Files : 
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/BucketMapJoinOptimizer.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/SortedMergeBucketMapJoinOptimizer.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/PrunedPartitionList.java
* /hive/trunk/ql/src/test/queries/clientpositive/bucketmapjoin2.q
* /hive/trunk/ql/src/test/results/clientpositive/bucketmapjoin2.q.out
* /hive/trunk/ql/src/test/results/clientpositive/bucketmapjoin_negative2.q.out

                
> Support Bucketed mapjoin on partitioned table which has two or more partitions
> ------------------------------------------------------------------------------
>
>                 Key: HIVE-3210
>                 URL: https://issues.apache.org/jira/browse/HIVE-3210
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>    Affects Versions: 0.10.0
>            Reporter: Navis
>            Assignee: Navis
>            Priority: Minor
>             Fix For: 0.10.0
>
>
> Bucketed mapjoin on multiple partition seemed to have no reason to be prohibited and even safer than doing simple mapjoin.

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