[
https://issues.apache.org/jira/browse/HIVE-17710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koifman updated HIVE-17710:
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Release Note: The LockManager which is installed automatically when
enabling Acid (hive.txn.manager=org.apache.hadoop.hive.ql.lockmgr.DbTxnManager)
does not lock any External Tables since Hive has no control over what is
modifying the data in such tables.
Status: Resolved (was: Patch Available)
no related failures
committed to master (fixed checkstyle nags)
thanks Alan for the rewiew
> 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
> Fix For: 3.0.0
>
> Attachments: HIVE-17710.01.patch, HIVE-17710.02.patch,
> HIVE-17710.03.patch, HIVE-17710.04.patch, HIVE-17710.04.patch
>
>
> 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)
