[
https://issues.apache.org/jira/browse/HIVE-22351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16954225#comment-16954225
]
Hive QA commented on HIVE-22351:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12983293/HIVE-22351.2.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 17541 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/19045/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/19045/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-19045/
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
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12983293 - PreCommit-HIVE-Build
> Fix incorrect threaded ObjectStore usage in TestObjectStore
> -----------------------------------------------------------
>
> Key: HIVE-22351
> URL: https://issues.apache.org/jira/browse/HIVE-22351
> Project: Hive
> Issue Type: Bug
> Affects Versions: 4.0.0
> Reporter: John Sherman
> Assignee: John Sherman
> Priority: Major
> Fix For: 4.0.0
>
> Attachments: HIVE-22351.1.patch, HIVE-22351.2.patch
>
>
> TestObjectStore#testConcurrentDropPartitions shares the same ObjectStore
> object across two threads doing concurrent drops. ObjectStore isn't thread
> safe. I've seen occasional deadlocks where one thread is rolling back and
> another is trying to commit with each thread waiting on the other (one is
> holding an object lock via a synchronized method and another is holding the
> ExecutionContextThreadedImpl lock). I think the intent is to test
> dropPartition behavior and ensure the backing DB receives a rollback or abort
> on conflicting drops.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
