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 2018/12/18 16:00:00 UTC

[jira] [Updated] (HIVE-21043) Enable move optimization for cloud replication with strict managed tables.

     [ https://issues.apache.org/jira/browse/HIVE-21043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sankar Hariappan updated HIVE-21043:
------------------------------------
    Summary: Enable move optimization for cloud replication with strict managed tables.  (was: Enable move optimization for replicating to cloud based cluster with strict managed tables.)

> 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
>         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)