Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 4 Dec 2012 10:50:57 +0000 (UTC)
From: "Namit Jain (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <549190473.58296.1354618257833.JavaMail.jiratomcat@arcas>
In-Reply-To: <111613769.4237.1349415407689.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (HIVE-3537) release locks at the end of move tasks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Namit Jain updated HIVE-3537:
-----------------------------

    Status: Patch Available  (was: Open)

comments addressed
                
> release locks at the end of move tasks
> --------------------------------------
>
>                 Key: HIVE-3537
>                 URL: https://issues.apache.org/jira/browse/HIVE-3537
>             Project: Hive
>          Issue Type: Bug
>          Components: Locking, Query Processor
>            Reporter: Namit Jain
>            Assignee: Namit Jain
>         Attachments: hive.3537.1.patch, hive.3537.2.patch
>
>
> Look at HIVE-3106 for details.
> In order to make sure that concurrency is not an issue for multi-table 
> inserts, the current option is to introduce a dependency task, which thereby
> delays the creation of all partitions. It would be desirable to release the
> locks for the outputs as soon as the move task is completed. That way, for
> multi-table inserts, the concurrency can be enabled without delaying any 
> table.
> Currently, the movetask contains a input/output, but they do not seem to be
> populated correctly.

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