[
https://issues.apache.org/jira/browse/HIVE-23413?focusedWorklogId=480705&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-480705
]
ASF GitHub Bot logged work on HIVE-23413:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Sep/20 09:43
Start Date: 09/Sep/20 09:43
Worklog Time Spent: 10m
Work Description: pvary commented on pull request #1220:
URL: https://github.com/apache/hive/pull/1220#issuecomment-689452296
> Checked, however I'm not sure if it is a good idea to give the end user
the option to completely disable the locking. They could end up shooting
themselves in the foot.
Administrator could add it to the restricted parameters which can not be set
by the user, so a customer can turn off if they feel it is problematic.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 480705)
Time Spent: 1h 10m (was: 1h)
> 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
> Labels: pull-request-available
> Attachments: HIVE-23413.1.patch, HIVE-23413.2.patch
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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)
