You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Chaoyu Tang (JIRA)" <ji...@apache.org> on 2014/12/23 19:46:13 UTC

[jira] [Created] (HIVE-9199) Excessive exclusive lock used in some DDLs with DummyTxnManager

Chaoyu Tang created HIVE-9199:
---------------------------------

             Summary: Excessive exclusive lock used in some DDLs with DummyTxnManager
                 Key: HIVE-9199
                 URL: https://issues.apache.org/jira/browse/HIVE-9199
             Project: Hive
          Issue Type: Bug
          Components: Locking
            Reporter: Chaoyu Tang
            Assignee: Chaoyu Tang


In DummyTxnManager, the lockMode for a WriteEntity (e.g. database, table) is determined by "complete" instead of its writeType. But since DDL output WriteEntity is usually complete, some DDL operations might be given exclusive locks which are actually not needed, which causes unnecessary locking contention. For example, in createTable, DummyTxnManager suggests an exclusive lock to table database writeentity since it is complete.



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