[
https://issues.apache.org/jira/browse/HIVE-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306045#comment-14306045
]
Brock Noland commented on HIVE-8136:
------------------------------------
Hi,
I am wondering if we cannot reduce the scope of locks for a few select cases.
For example:
{{alter table add partition}}
{{alter table [part...] set location}}
The hms database will take care of handling the case where the someone is
reading the list of partitions while this operation occurs. For someone who
started an a job prior to this operation, they've already gotten their list of
paths to read.
I do see issues with dropping partitions since that deletes data which might
be, being read.
What are your thoughts?
> Reduce table locking
> --------------------
>
> Key: HIVE-8136
> URL: https://issues.apache.org/jira/browse/HIVE-8136
> Project: Hive
> Issue Type: Sub-task
> Reporter: Brock Noland
> Assignee: Ferdinand Xu
> Attachments: HIVE-8136.patch
>
>
> When using ZK for concurrency control, some statements require an exclusive
> table lock when they are atomic. Such as setting a tables location.
> This JIRA is to analyze the scope of statements like ALTER TABLE and see if
> we can reduce the locking required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
