[
https://issues.apache.org/jira/browse/HIVE-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229508#comment-14229508
]
Wan Chang commented on HIVE-8192:
---------------------------------
Sorry I misunderstanded the lock model of insert into statement. It should
require a X rather than a S lock.
> 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.0, 0.13.1
> Environment: hive0.13.1
> Reporter: Wan Chang
> Priority: Minor
> Labels: patch
> Attachments: HIVE-8192.2.patch, HIVE-8192.3.patch, HIVE-8192.4.patch,
> HIVE-8192.5.patch
>
>
> 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)
