Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.0.0
-
None
-
None
Description
Hive TransactionManager currently has a mix of lock based and optimistic concurrency management techniques (which at times overlap).
For inserts with Dynamic Partitions that represents update/merge it acquires locks on each existing partition which can flood the metastore DB.
Need to clean up the logical model and the implementation.
This will be an umbrella Jira for this
Attachments
Issue Links
- relates to
-
HIVE-19961 Add partition if exists on transactional CRUD table acquires X lock
- Open
-
HIVE-20435 Failed Dynamic Partition Insert into insert only table may loose transaction metadata
- Closed
-
HIVE-18772 Make Acid Cleaner use MIN_HISTORY_LEVEL
- Closed
-
HIVE-16139 Clarify Acid concurrency model
- Open