[
https://issues.apache.org/jira/browse/HIVE-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461553#comment-16461553
]
Eugene Koifman edited comment on HIVE-18131 at 5/2/18 7:56 PM:
---------------------------------------------------------------
the patch only adds a test to make sure we acquire X lock for acid tables.
changing this to create a new base_x will be done in 3.1 ideally after we add a
new X_write lock that blocks other writes but not reads.
[~prasanth_j] could you review please
was (Author: ekoifman):
the patch only adds a test to make sure we acquire X lock for acid tables.
changing this to create a new base_x will be done in 3.1 ideally after we add a
new X_write lock that blocks other writes but not reads.
> Truncate table for Acid tables
> ------------------------------
>
> Key: HIVE-18131
> URL: https://issues.apache.org/jira/browse/HIVE-18131
> Project: Hive
> Issue Type: New Feature
> Components: Transactions
> Reporter: Eugene Koifman
> Assignee: Eugene Koifman
> Priority: Major
> Attachments: HIVE-18131.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)
