[
https://issues.apache.org/jira/browse/HIVE-21043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724193#comment-16724193
]
ASF GitHub Bot commented on HIVE-21043:
---------------------------------------
Github user sankarh closed the pull request at:
https://github.com/apache/hive/pull/508
> Enable move optimization for cloud replication 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
> Fix For: 4.0.0
>
> 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)
