Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Mon, 1 Oct 2012 15:30:07 +1100 (NCT)
From: "Namit Jain (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <1365586701.146751.1349065807765.JavaMail.jiratomcat@arcas>
In-Reply-To: <509688551.81276.1347643688518.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (HIVE-3467) BucketMapJoinOptimizer should optimize
 joins on partition columns
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Namit Jain updated HIVE-3467:
-----------------------------

    Status: Open  (was: Patch Available)

comments on phabricator
                
> BucketMapJoinOptimizer should optimize joins on partition columns
> -----------------------------------------------------------------
>
>                 Key: HIVE-3467
>                 URL: https://issues.apache.org/jira/browse/HIVE-3467
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.10.0
>            Reporter: Kevin Wilfong
>            Assignee: Zhenxiao Luo
>         Attachments: HIVE-3467.1.patch.txt
>
>
> Consider the query:
> SELECT * FROM t1 JOIN t2 on t1.part = t2.part and t1.key = t2.key;
> Where t1 and t2 are partitioned by part and bucketed by key.
> Suppose part take values 1 and 2 and t1 and t2 are bucketed into 2 buckets.
> The bucket map join optimizer will put the first bucket of part=1 and part=2 partitions of t2 into the same mapper as that of part=1 partition of t1.  It will do the same for the part=2 partition of t1.
> It could take advantage of the partition values and send the first bucket of only the part=1 partitions of t1 and t2 into one mapper and the first bucket of only the part=2 partitions into another.

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