hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-10242) ACID: insert overwrite prevents create table command
Date Sun, 12 Apr 2015 19:28:12 GMT


Hive QA commented on HIVE-10242:

{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 14 failed/errored test(s), 8678 tests executed
*Failed tests:*
- did not produce a TEST-*.xml file
- did not produce a TEST-*.xml file
- did not produce a TEST-*.xml file
- did not produce a TEST-*.xml file
- did not produce a TEST-*.xml file
- did not produce a TEST-*.xml file
- did not produce a TEST-*.xml file
- did not produce a TEST-*.xml file
TestMinimrCliDriver-list_bucket_dml_10.q-bucket_num_reducers.q-bucket6.q-and-1-more - did
not produce a TEST-*.xml file
- did not produce a TEST-*.xml file
- did not produce a TEST-*.xml file
TestMinimrCliDriver-ql_rewrite_gbtoidx.q-smb_mapjoin_8.q - did not produce a TEST-*.xml file
TestMinimrCliDriver-schemeAuthority2.q-bucket4.q-input16_cc.q-and-1-more - did not produce
a TEST-*.xml file

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: 14 tests failed

This message is automatically generated.

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

> ACID: insert overwrite prevents create table command
> ----------------------------------------------------
>                 Key: HIVE-10242
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 1.0.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>         Attachments: HIVE-10242.2.patch, HIVE-10242.3.patch, HIVE-10242.patch
> 1. insert overwirte table DB.T1 select ... from T2: this takes X lock on DB.T1 and S
lock on T2.
> X lock makes sense because we don't want anyone reading T1 while it's overwritten. S
lock on T2 prevents if from being dropped while the query is in progress.
> 2. create table DB.T3: takes S lock on DB.
> This S lock gets blocked by X lock on T1. S lock prevents the DB from being dropped while
create table is executed.
> If the insert statement is long running, this blocks DDL ops on the same database.  This
is a usability issue.  
> There is no good reason why X lock on a table within a DB and S lock on DB should be
in conflict.  
> (this is different from a situation where X lock is on a partition and S lock is on the
table to which this partition belongs.  Here it makes sense.  Basically there is no SQL way
to address all tables in a DB but you can easily refer to all partitions of a table)

This message was sent by Atlassian JIRA

View raw message