You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Hive QA (Jira)" <ji...@apache.org> on 2020/06/03 12:15:00 UTC

[jira] [Commented] (HIVE-23413) Create a new config to skip all locks

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

Hive QA commented on HIVE-23413:
--------------------------------



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

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

{color:green}SUCCESS:{color} +1 due to 17097 tests passed

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

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: 13004696 - PreCommit-HIVE-Build

> Create a new config to skip all locks
> -------------------------------------
>
>                 Key: HIVE-23413
>                 URL: https://issues.apache.org/jira/browse/HIVE-23413
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Peter Varga
>            Assignee: Peter Varga
>            Priority: Major
>         Attachments: HIVE-23413.1.patch, HIVE-23413.2.patch
>
>
> From time-to-time some query is blocked on locks which should not.
> To have a quick workaround for this we should have a config which the user can set in the session to disable acquiring/checking locks, so we can provide it immediately and then later investigate and fix the root cause.



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