hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-17527) Support replication for rename/move table across database
Date Wed, 13 Sep 2017 19:05:02 GMT

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

ASF GitHub Bot commented on HIVE-17527:
---------------------------------------

GitHub user sankarh opened a pull request:

    https://github.com/apache/hive/pull/250

    HIVE-17527: Support replication for rename/move table across database

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sankarh/hive HIVE-17527

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hive/pull/250.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #250
    
----
commit 223682c15e418b5cfbfecf71575229722f3dca25
Author: Sankar Hariappan <mailtosankarh@gmail.com>
Date:   2017-09-13T19:03:30Z

    HIVE-17527: Support replication for rename/move table across database

----


> Support replication for rename/move table across database
> ---------------------------------------------------------
>
>                 Key: HIVE-17527
>                 URL: https://issues.apache.org/jira/browse/HIVE-17527
>             Project: Hive
>          Issue Type: Sub-task
>          Components: repl
>    Affects Versions: 2.1.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>              Labels: DR, pull-request-available, replication
>             Fix For: 3.0.0
>
>
> Rename/move table across database should be supported for replication. The scenario is
as follows.
> 1. Create 2 databases (db1 and db2) in source cluster.
> 2. Create the table db1.tbl1.
> 3. Run bootstrap replication for db1 and db2 to target cluster.
> 4. Rename db1.tbl1 to db2.tbl1 in source.
> 5. Run incremental replication for both db1 and db2.
> - db1 dump missed the rename table operation as no event is generated for db1. So, table
exist after load.
> - db2 load skips the rename event as the source table is missing in target.



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

Mime
View raw message