[
https://issues.apache.org/jira/browse/HIVE-23293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17095907#comment-17095907
]
Hive QA commented on HIVE-23293:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/13001571/HIVE-23293.3.patch
{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 17181 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/22019/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/22019/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-22019/
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: 13001571 - PreCommit-HIVE-Build
> Locks: Implement zero-wait readers
> -----------------------------------
>
> Key: HIVE-23293
> URL: https://issues.apache.org/jira/browse/HIVE-23293
> Project: Hive
> Issue Type: Sub-task
> Reporter: Denys Kuzmenko
> Assignee: Denys Kuzmenko
> Priority: Major
> Attachments: HIVE-23293.1.patch, HIVE-23293.2.patch,
> HIVE-23293.3.patch
>
>
> With a new lock type (EXCL_WRITE) for INSERT_OVERWRITE, SHARED_READ does not
> have to wait for any lock - it can fails fast for a pending EXCLUSIVE,
> because even if there is an EXCL_WRITE or SHARED_WRITE pending, there's no
> semantic reason to wait for them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
