hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-17710) LockManager should only lock Managed tables
Date Thu, 07 Dec 2017 23:45:00 GMT

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

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

It seems reasonable to lock views.  We don't want someone dropping a view while a query is
using it.  For virtual views this could be removed after compilation is finished.  In the
case of materialized view we need to make sure that refreshing the view does not happen in
the midst of a query reading the view (or if it does, the view itself is versioned so that
the query gets the old version and not the new).

> 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)

Mime
View raw message