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] [Commented] (HIVE-20708) Load (dumped) an external table as an external table on target with the same location as on the source
Date Tue, 16 Oct 2018 08:51:00 GMT

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

ASF GitHub Bot commented on HIVE-20708:
---------------------------------------

GitHub user ashutosh-bapat opened a pull request:

    https://github.com/apache/hive/pull/447

    HIVE-20708: Load an external table as an external table on target with the same location
as  on the source

    Dump an external table as an external table.
    
    When loading an external table set the location of the target table same as the location
of source,
    but relative to the file system of the target location. IOW, the scheme, authority of
the target
    location is same as the target file system but the path relative to the file system is
same as the
    source.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ashutosh-bapat/hive hive20708

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hive/pull/447.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #447
    
----
commit c076bbbd2b0fd1b193ac51a1595911a80324b923
Author: Ashutosh Bapat <ashutosh.bapat.oss@...>
Date:   2018-10-15T05:09:05Z

    HIVE-20708: Load an external table as an external table on target with the same location
as
    on the source
    
    Dump an external table as an external table.
    
    When loading an external table set the location of the target table same as the location
of source,
    but relative to the file system of the target location. IOW, the scheme, authority of
the target
    location is same as the target file system but the path relative to the file system is
same as the
    source.

----


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

Mime
View raw message