[
https://issues.apache.org/jira/browse/HIVE-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuefu Zhang updated HIVE-9199:
------------------------------
Resolution: Fixed
Fix Version/s: 0.15.0
Status: Resolved (was: Patch Available)
Committed to trunk. Thanks, Chaoyu!
> 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
> Fix For: 0.15.0
>
> Attachments: HIVE-9199.patch
>
>
> 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)
