Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 14 Mar 2014 18:42:43 +0000 (UTC)
From: "Siddharth Seth (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12700625.1394504595165.71603.1394822563152@arcas>
In-Reply-To: <JIRA.12700625.1394504595165@arcas>
References: <JIRA.12700625.1394504595165@arcas>
Subject: [jira] [Updated] (HIVE-6613) Control when spcific Inputs / Outputs
 are started
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Siddharth Seth updated HIVE-6613:
---------------------------------

    Status: Patch Available  (was: Open)

> Control when spcific Inputs / Outputs are started
> -------------------------------------------------
>
>                 Key: HIVE-6613
>                 URL: https://issues.apache.org/jira/browse/HIVE-6613
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>         Attachments: HIVE-6613.2.txt, TEZ-6613.1.txt
>
>
> When running with Tez - a couple of enhancement are possible
> 1) Avoid re-fetching data in case of MapJoins - since the data is likely to be cached after the first run (container re-use for the same query)
> 2) Start Outputs only after required Inputs are ready - specifically useful in case of Reduce - where shuffle requires a large memory, and the Output (if it's a sorted output) also requires a fair amount of memory.


--
This message was sent by Atlassian JIRA
(v6.2#6252)