Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 11 Sep 2014 06:10:34 +0000 (UTC)
From: "Gunther Hagleitner (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12740590.1410377597000.7004.1410415834298@Atlassian.JIRA>
In-Reply-To: <JIRA.12740590.1410377597000@Atlassian.JIRA>
References: <JIRA.12740590.1410377597000@Atlassian.JIRA>
 <JIRA.12740590.1410377597674@arcas>
Subject: [jira] [Updated] (HIVE-8042) Optionally allow move tasks to run in
 parallel
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gunther Hagleitner updated HIVE-8042:
-------------------------------------
    Status: Patch Available  (was: Open)

> Optionally allow move tasks to run in parallel
> ----------------------------------------------
>
>                 Key: HIVE-8042
>                 URL: https://issues.apache.org/jira/browse/HIVE-8042
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Gunther Hagleitner
>            Assignee: Gunther Hagleitner
>         Attachments: HIVE-8042.1.patch, HIVE-8042.2.patch, HIVE-8042.3.patch
>
>
> hive.exec.parallel allows one to run different stages of a query in parallel. However that applies only to map-reduce tasks. When using large multi insert queries there are many MoveTasks that are all executed in sequence on the client. There's no real reason for that - they could be run in parallel as well (i.e.: the stage graph captures the dependencies and knows which tasks can happen in parallel).


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