hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sankar Hariappan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-21043) Enable move optimization for replicating to cloud based cluster with strict managed tables.
Date Fri, 14 Dec 2018 08:59:00 GMT

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

Sankar Hariappan updated HIVE-21043:
------------------------------------
    Description: 
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.


  was:
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 optimisation is disabled.



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

Mime
View raw message