[
https://issues.apache.org/jira/browse/HIVE-17710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282746#comment-16282746
]
Eugene Koifman commented on HIVE-17710:
---------------------------------------
The materialization of the view is versioned.
I don't think we can lock anything during compilation since we have to have a
query plan to know what to lock.
I'm not sure how much value there is in protecting from a drop. Suppose there
is a read op and a concurrent drop op is issued. Yes the drop will block but
the next attempt to read will still get an error. In other words the type of
admin op like removing some object needs to coordinated - a read lock in this
case seems of minor help if someone issued a drop by mistake.
> LockManager should only lock Managed 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)
