[HIVE-20137] Truncate for Transactional tables should use base_x

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 4.0.0-alpha-1
• Component/s: Transactions
• Labels: pull-request-available
• Target Version/s: 4.0.0
• Assignee: Peter Varga
• Reporter: Eugene Koifman
• Created: 10/Jul/18 22:17
• Updated: 17/Nov/22 08:54
• Resolved: 08/Oct/20 12:42

Description

This is a follow up to HIVE-19387.

Once we have a lock that blocks writers but not readers (HIVE-19369), it would make sense to make truncate create a new base_x, where is x is a writeId in current txn - the same as Insert Overwrite does.

This would mean it can work w/o interfering with existing writers.

Issue Links

• is blocked by: HIVE-19387 Truncate table for Acid tables conflicts with ResultSet cache
• links to: GitHub Pull Request #1532

Sub-Tasks

• Truncate optimization to avoid unnecessary per partition DB get operations: Closed
• Config used to enable non-blocking TRUNCATE is not properly propagated: Closed