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

Hive QA commented on HIVE-21602:
--------------------------------



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

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

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

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

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: 12965617 - PreCommit-HIVE-Build

> Dropping an external table created by migration case should delete the data 
> directory.
> --------------------------------------------------------------------------------------
>
>                 Key: HIVE-21602
>                 URL: https://issues.apache.org/jira/browse/HIVE-21602
>             Project: Hive
>          Issue Type: Test
>          Components: repl, Test
>    Affects Versions: 4.0.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>            Priority: Minor
>              Labels: DR, Replication, Test, pull-request-available
>         Attachments: HIVE-21602.01.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> For external table, if the table is dropped, the location is not removed. But 
> If the source table is managed and at target the table is converted to 
> external, then the table location should be removed if the table is dropped.
> Replication flow should set additional parameter 
> "external.table.purge"="true" for migration to external table.



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

Reply via email to