hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vaibhav Gumashta (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HIVE-20137) Truncate for Transactional tables should use base_x
Date Fri, 17 May 2019 19:26:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-20137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vaibhav Gumashta reassigned HIVE-20137:
---------------------------------------

    Assignee: Vaibhav Gumashta

> 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: Vaibhav Gumashta
>            Priority: Major
>
> 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
(v7.6.3#76005)

Mime
View raw message