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

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

GitHub user sankarh opened a pull request:

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

    HIVE-21043: Enable move optimization for replicating to cloud based cluster 
with strict managed tables.

    

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

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

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

    https://github.com/apache/hive/pull/508.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 #508
    
----
commit a3fd34c093b4ebc5672156d8bc7e6f4d426aee6d
Author: Sankar Hariappan <mailtosankarh@...>
Date:   2018-12-18T11:00:04Z

    HIVE-21043: Enable move optimization for replicating to cloud based cluster 
with strict managed tables.

----


> Enable move optimization for replicating to cloud based cluster with strict 
> managed tables.
> -------------------------------------------------------------------------------------------
>
>                 Key: HIVE-21043
>                 URL: https://issues.apache.org/jira/browse/HIVE-21043
>             Project: Hive
>          Issue Type: Sub-task
>          Components: repl
>    Affects Versions: 4.0.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>            Priority: Major
>              Labels: DR, pull-request-available
>         Attachments: HIVE-21043.01.patch
>
>
> If hive.repl.enable.move.optimization is set to true, then Hive REPL LOAD 
> avoids move operation and copy the data files directly to target location. 
> This is helpful for Cloud replication where the move is non-atomic and also 
> implemented as copy.
> Currently, if hive.strict.managed.tables is enabled at target and if 
> migration to transactional table is needed during REPL LOAD, then this 
> optimization is disabled.
> Need to support it.



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

Reply via email to