[ 
https://issues.apache.org/jira/browse/HIVE-23391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111329#comment-17111329
 ] 

Hive QA commented on HIVE-23391:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/13003351/HIVE-23391.4.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 1 failed/errored test(s), 17271 tests 
executed
*Failed tests:*
{noformat}
org.apache.hadoop.hive.metastore.txn.TestTxnHandler.allocateNextWriteIdRetriesAfterDetectingConflictingConcurrentInsert
 (batchId=247)
{noformat}

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/22460/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/22460/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-22460/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 1 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 13003351 - PreCommit-HIVE-Build

> Change requested lock for ALTER TABLE ADD COLUMN to DDL_SHARED
> --------------------------------------------------------------
>
>                 Key: HIVE-23391
>                 URL: https://issues.apache.org/jira/browse/HIVE-23391
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Zoltan Chovan
>            Assignee: Zoltan Chovan
>            Priority: Major
>             Fix For: 4.0.0
>
>         Attachments: HIVE-23391.2.patch, HIVE-23391.3.patch, 
> HIVE-23391.4.patch, HIVE-23391.patch
>
>
> A long running query can block a simple add column query, as the add column 
> will require a DDL_EXCLUSIVE lock currently. By changing this to a shared 
> lock, this metadata only query can be executed without having to wait for the 
> previous query to finish.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to