[
https://issues.apache.org/jira/browse/HIVE-20137?focusedWorklogId=491986&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-491986
]
ASF GitHub Bot logged work on HIVE-20137:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Sep/20 13:49
Start Date: 28/Sep/20 13:49
Worklog Time Spent: 10m
Work Description: pvargacl opened a new pull request #1532:
URL: https://github.com/apache/hive/pull/1532
### What changes were proposed in this pull request?
Truncate table for transactional tables no longer deletes all the data,
rather just creates an empty base dir.
### Why are the changes needed?
Faster truncate, it can allow concurrent reads
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
Tests were added
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 491986)
Remaining Estimate: 0h
Time Spent: 10m
> Truncate for Transactional tables should use base_x
> ---------------------------------------------------
>
> Key: HIVE-20137
> URL: https://issues.apache.org/jira/browse/HIVE-20137
> Project: Hive
> Issue Type: Improvement
> Components: Transactions
> Affects Versions: 3.0.0
> Reporter: Eugene Koifman
> Assignee: Peter Varga
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
