[HIVE-11716] Reading ACID table from non-acid session should raise an error

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.3.0, 2.1.0
• Component/s: Transactions
• Target Version/s: 1.3.0, 2.1.0
• Assignee: Wei Zheng
• Reporter: Eugene Koifman
• Created: 02/Sep/15 00:12
• Updated: 01/Oct/19 22:06
• Resolved: 04/Feb/16 00:26

Description

if someone performs a delete using DbTxnManager and than starts a new session with DummyTxnManager, then previously successfully deleted data will show up.

Once the logic to identify all acid tables being read is there, make sure that
Driver.recordValidTxns() called iff there ACID tables in the query.

We should also not allow writing to ACID table from non-acid session

Issue Links

• relates to: HIVE-12441 Driver.acquireLocksAndOpenTxn() should only call recordValidTxns() when needed
• supercedes: HIVE-12979 ErrorMsg.ACID_OP_ON_NONACID_TXNMGR should include table name