[HIVE-13795] TxnHandler should know if operation is using dynamic partitions

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 1.3.0, 2.1.0
• Component/s: Transactions
• Target Version/s: 1.3.0, 3.0.0
• Assignee: Unassigned
• Reporter: Eugene Koifman
• Created: 19/May/16 20:02
• Updated: 28/Jul/21 14:13

Description

TxnHandler.checkLock() see more comments around "isPartOfDynamicPartitionInsert". If TxnHandler knew whether it is being called as part of an op running with dynamic partitions, it could be more efficient. In that case we don't have to write to TXN_COMPONENTS at all during lock acquisition. Conversely, if not running with DynPart then, we can kill current txn on lock grant rather than wait until commit time.

if addDynamicPartitions() also knew about DynPart it could eliminate the Delete from Txn_components... statement

This is an important perf optimization when it allows us to detect that concurrent txns will have a WW conflict early

Issue Links

• depends upon: HIVE-14943 Base Implementation
• is related to: HIVE-17821 TxnHandler.enqueueLockWithRetry() should not write TXN_COMPONENTS if partName=null and table is partitioned
• is related to: HIVE-13622 WriteSet tracking optimizations