You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Ferdinand Xu (JIRA)" <ji...@apache.org> on 2015/04/15 09:27:58 UTC

[jira] [Updated] (HIVE-8136) Reduce table locking

     [ https://issues.apache.org/jira/browse/HIVE-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ferdinand Xu updated HIVE-8136:
-------------------------------
    Attachment: HIVE-8136.1.patch

As discussed offline with [~brocknoland], for altering location, anyone who is reading has already gotten the location they are reading from, the new location is irrelevant to them and it is relevant to writers. [~brocknoland] and [~szehon], could you help me review this patch and check it in? Thank you!

> 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.1.patch, 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)