[
https://issues.apache.org/jira/browse/HIVE-23413?focusedWorklogId=481938&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-481938
]
ASF GitHub Bot logged work on HIVE-23413:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Sep/20 07:39
Start Date: 11/Sep/20 07:39
Worklog Time Spent: 10m
Work Description: pvary commented on pull request #1220:
URL: https://github.com/apache/hive/pull/1220#issuecomment-690931518
> @pvary So what is the conclusion? Should I add it to the restricted list
by default? Or will you merge this, as is?
I would like to see an agreement here. This is more like a democratic
process, than autocratic :)
I still think this will become useful immediately when someone has a problem
with the too restrictive locking. If in doubt we might just add this to
HIVE_CONF_RESTRICTED_LIST, so no rouge user can use this unless the
administrator explicitly allows the usage of the new config.
But this is only me, others might different opinions
----------------------------------------------------------------
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: 481938)
Time Spent: 1.5h (was: 1h 20m)
> 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: 1.5h
> 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)
