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

Posted to issues@hive.apache.org by "Alan Gates (JIRA)" <ji...@apache.org> on 2017/10/05 19:59:00 UTC

[jira] [Commented] (HIVE-17710) LockManager and External tables

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

Alan Gates commented on HIVE-17710:
-----------------------------------

Since part of the notion of external tables is that data can be (often is?) written from outside Hive and when a drop table is done the data isn't removed, I'm not even sure what locking means for an external table.  At most it would mean locking the table structure, but not the data.   It seems reasonable to say we don't lock them.

> LockManager and External tables
> -------------------------------
>
>                 Key: HIVE-17710
>                 URL: https://issues.apache.org/jira/browse/HIVE-17710
>             Project: Hive
>          Issue Type: New Feature
>          Components: Transactions
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>
> should the LM take locks on External tables?  Out of the box Acid LM is being conservative which can cause throughput issues.
> A better strategy may be to exclude External tables but enable explicit "lock table/partition <lock mode>" command (only on external tables?).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)