Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 16 Dec 2014 11:43:13 +0000 (UTC)
From: "Rui Li (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12761670.1418608508000.32744.1418730193355@Atlassian.JIRA>
In-Reply-To: <JIRA.12761670.1418608508000@Atlassian.JIRA>
References: <JIRA.12761670.1418608508000@Atlassian.JIRA>
 <JIRA.12761670.1418608508683@arcas>
Subject: [jira] [Updated] (HIVE-9097) Support runtime skew join for more
 queries [Spark Branch]
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rui Li updated HIVE-9097:
-------------------------
    Status: Patch Available  (was: Open)

> Support runtime skew join for more queries [Spark Branch]
> ---------------------------------------------------------
>
>                 Key: HIVE-9097
>                 URL: https://issues.apache.org/jira/browse/HIVE-9097
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Rui Li
>            Assignee: Rui Li
>         Attachments: HIVE-9097.1-spark.patch
>
>
> After HIVE-8913, runtime skew join is enabled for spark. But currently the optimization only supports the simplest case where join is the leaf ReduceWork in a work graph. This is because the results from the original join and the conditional map join have to be unioned to feed to downstream works, which can be a little tricky for spark.
> This JIRA is to research and find a way to relax the above restriction. A possible solution is to break the original task into two tasks on the join work, and insert the conditional task in between.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)