[ 
https://issues.apache.org/jira/browse/HIVE-19387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540633#comment-16540633
 ] 

Hive QA commented on HIVE-19387:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12931078/HIVE-19387.01.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 14643 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/12536/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/12536/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-12536/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12931078 - PreCommit-HIVE-Build

> 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: Blocker
>         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)

Reply via email to