Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 19 Sep 2014 20:26:33 +0000 (UTC)
From: "cw (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12742835.1411158345000.81034.1411158393854@Atlassian.JIRA>
In-Reply-To: <JIRA.12742835.1411158345000@Atlassian.JIRA>
References: <JIRA.12742835.1411158345000@Atlassian.JIRA>
 <JIRA.12742835.1411158345788@arcas>
Subject: [jira] [Created] (HIVE-8192) Check DDL's writetype in
 DummyTxnManager
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

cw created HIVE-8192:
------------------------

             Summary: Check DDL's writetype in DummyTxnManager
                 Key: HIVE-8192
                 URL: https://issues.apache.org/jira/browse/HIVE-8192
             Project: Hive
          Issue Type: Bug
          Components: Locking
    Affects Versions: 0.13.1, 0.13.0
         Environment: hive0.13.1
            Reporter: cw
            Priority: Minor
             Fix For: 0.14.0


The patch of HIVE-6734 added some DDL writetypes and checked DDL writetype in DbTxnManager.java.
We use DummyTxnManager as the default value of hive.txn.manager in hive-site.xml. We noticed that the operation of CREATE TEMPORARY FUNCTION has a DLL_NO_LOCK writetype but it requires a EXCLUSIVE lock. If we try to create a temporary function while there's a SELECT is processing at the same database, then the console will print 'conflicting lock present for default mode EXCLUSIVE' and the CREATE TEMPORARY FUNCTION operation won't get the lock until the SELECT is done. Maybe it's a good idea to check the DDL's writetype in DummyTxnManager too.


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