You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sankar Hariappan (JIRA)" <ji...@apache.org> on 2017/07/03 16:43:00 UTC

[jira] [Comment Edited] (HIVE-16750) Support change management for rename table/partition.

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

Sankar Hariappan edited comment on HIVE-16750 at 7/3/17 4:42 PM:
-----------------------------------------------------------------

Added 03.patch with fix for the test failure of encryption_move_tbl.q.
Other failures are irrelevant to the change.



was (Author: sankarh):
Added 03.patch with fix for the test failure of encryption_move_tbl.q.
Other failures are irrelevant to the change.

> Support change management for rename table/partition.
> -----------------------------------------------------
>
>                 Key: HIVE-16750
>                 URL: https://issues.apache.org/jira/browse/HIVE-16750
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Hive, repl
>    Affects Versions: 2.1.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>              Labels: DR, replication
>             Fix For: 3.0.0
>
>         Attachments: HIVE-16750.01.patch, HIVE-16750.02.patch, HIVE-16750.03.patch
>
>
> Currently, rename table/partition updates the data location by renaming the directory which is equivalent to moving files to new path and delete old path. So, this should trigger move of files into $CMROOT.
> Scenario:
> 1. Create a table (T1)
> 2. Insert a record
> 3. Rename the table(T1 -> T2)
> 4. Repl Dump till Insert.
> 5. Repl Load from the dump.
> 6. Target DB should have table T1 with the record.
> Similar scenario with rename partition as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)