hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-19387) Truncate table for Acid tables conflicts with ResultSet cache
Date Tue, 10 Jul 2018 22:40:00 GMT

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

Eugene Koifman updated HIVE-19387:
----------------------------------
    Attachment: HIVE-19387.01.patch

> Truncate table for Acid tables conflicts with ResultSet cache
> -------------------------------------------------------------
>
>                 Key: HIVE-19387
>                 URL: https://issues.apache.org/jira/browse/HIVE-19387
>             Project: Hive
>          Issue Type: New Feature
>          Components: Transactions
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>            Priority: Major
>         Attachments: HIVE-19387.01.patch
>
>
> How should this work?  Should it work like Insert Overwrite T select * from T where 1=2?
> This should create a new empty base_x/ and thus operate w/o violating Snapshot Isolation
semantics.
> This makes sense for specific partition or unpartitioned table.  What about "Truncate
T" where T is partitioned?  Is the expectation to wipe out all partition info or to make each
partition empty?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message