Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 655C511FD0 for ; Wed, 10 Sep 2014 19:41:37 +0000 (UTC) Received: (qmail 61203 invoked by uid 500); 10 Sep 2014 19:41:34 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 61131 invoked by uid 500); 10 Sep 2014 19:41:34 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 61118 invoked by uid 500); 10 Sep 2014 19:41:33 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 61115 invoked by uid 99); 10 Sep 2014 19:41:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Sep 2014 19:41:33 +0000 Date: Wed, 10 Sep 2014 19:41:33 +0000 (UTC) From: "Xuefu Zhang (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-8042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128977#comment-14128977 ] Xuefu Zhang commented on HIVE-8042: ----------------------------------- This seems certainly nice to have. However, I'm wondering why we need a flag for this rather just taking hive.exec.parallel? If the dependency is set correctly, I don't see any harm of running move task in parallel. If we have a flag for each task type, it seems the number of options are exploding. > 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.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) > Proposal here is to create a new config var: > hive.exec.parallel.movetask > When set to true it run movetasks in parallel also. -- This message was sent by Atlassian JIRA (v6.3.4#6332)