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

ASF GitHub Bot updated HIVE-20708:
----------------------------------
    Labels: pull-request-available  (was: )

> Load (dumped) an external table as an external table on target with the same 
> location as on the source
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-20708
>                 URL: https://issues.apache.org/jira/browse/HIVE-20708
>             Project: Hive
>          Issue Type: Improvement
>          Components: repl
>            Reporter: Ashutosh Bapat
>            Assignee: Ashutosh Bapat
>            Priority: Major
>              Labels: pull-request-available
>
> External tables are currently mapped to managed tables on target. A lot of 
> jobs in user environment are dependent upon locations specified in external 
> table definitions to run, hence, the path for external tables on the target 
> and on the source are expected to be the same. An external table being loaded 
> as a  managed table makes it difficult for failover (Controlled Failover) / 
> failback since there is no option of moving data from managed to external 
> table. So the external table replicated to target cluster needs to be kept as 
> external table with same location as on the source.



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

Reply via email to