[HIVE-19382] Acquire locks before generating valid transaction list for some operations

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.1.0, 4.0.0-alpha-1
• Component/s: Transactions
• Assignee: Jesús Camacho Rodríguez
• Reporter: Jesús Camacho Rodríguez
• Created: 02/May/18 02:42
• Updated: 27/Feb/24 22:23
• Resolved: 10/Jun/18 06:34

Description

To ensure correctness, in particular for operations that require exclusive (INSERT OVERWRITE) and semishared (UPDATE/DELETE) locks.

This is a temporary fix till lock acquisition is moved before analyze in HIVE-18948.

With this fix, system proceed as follows. The driver will acquire the snapshot, compile the query wrt that snapshot, and then, it will acquire locks. If snapshot is still valid, it will continue as usual. But if snapshot is not valid anymore, it will recompile the query.

This is easier to implement than full solution described in HIVE-18948 because we do not need to move the logic to extract the read/write entities from a query before compilation (actually while parsing).

Issue Links

• is caused by: HIVE-18825 Define ValidTxnList before starting query optimization
• is related to: HIVE-19907 Driver.isValidTxnListState should rely on global txn list
• is related to: HIVE-19859 Inspect lock components for DBHiveLock while verifying whether transaction list is valid
• is related to: HIVE-19876 Multiple fixes for Driver.isValidTxnListState
• relates to: HIVE-18948 Acquire locks before generating the valid transaction list
• links to: RB link