hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-8192) Check DDL's writetype in DummyTxnManager
Date Mon, 01 Dec 2014 09:55:12 GMT


Hive QA commented on HIVE-8192:

{color:red}Overall{color}: -1 at least one tests failed

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 6696 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 4 tests failed

This message is automatically generated.

ATTACHMENT ID: 12684356 - PreCommit-HIVE-TRUNK-Build

> Check DDL's writetype in DummyTxnManager
> ----------------------------------------
>                 Key: HIVE-8192
>                 URL:
>             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
> 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

This message was sent by Atlassian JIRA

View raw message