hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
Date Fri, 15 Feb 2019 11:16:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-20708?focusedWorklogId=199164&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-199164
]

ASF GitHub Bot logged work on HIVE-20708:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 15/Feb/19 11:15
            Start Date: 15/Feb/19 11:15
    Worklog Time Spent: 10m 
      Work Description: ashutosh-bapat commented on pull request #447: HIVE-20708: Load an
external table as an external table on target with the same location as  on the source
URL: https://github.com/apache/hive/pull/447
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 199164)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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
>         Attachments: HIVE-20708.01, HIVE-20708.02, HIVE-20708.03
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)

Mime
View raw message