hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (HIVE-20137) Truncate for Transactional tables should use base_x
Date Tue, 29 Sep 2020 20:17:00 GMT


ASF GitHub Bot logged work on HIVE-20137:

                Author: ASF GitHub Bot
            Created on: 29/Sep/20 20:16
            Start Date: 29/Sep/20 20:16
    Worklog Time Spent: 10m 
      Work Description: pvargacl commented on pull request #1532:

   @pvary @kuczoram could you review this patch?

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:

Issue Time Tracking

    Worklog Id:     (was: 492651)
    Time Spent: 20m  (was: 10m)

> Truncate for Transactional tables should use base_x
> ---------------------------------------------------
>                 Key: HIVE-20137
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Transactions
>    Affects Versions: 3.0.0
>            Reporter: Eugene Koifman
>            Assignee: Peter Varga
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  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

View raw message