You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Gary Helmling (JIRA)" <ji...@apache.org> on 2016/01/04 09:25:39 UTC

[jira] [Updated] (HBASE-15038) ExportSnapshot should support separate configurations for source and destination clusters

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

Gary Helmling updated HBASE-15038:
----------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 1.2.1
                   1.3.0
                   2.0.0
           Status: Resolved  (was: Patch Available)

Committed to master, branch-1 and branch-1.2.

> ExportSnapshot should support separate configurations for source and destination clusters
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-15038
>                 URL: https://issues.apache.org/jira/browse/HBASE-15038
>             Project: HBase
>          Issue Type: Improvement
>          Components: mapreduce, snapshots
>            Reporter: Gary Helmling
>            Assignee: Gary Helmling
>             Fix For: 2.0.0, 1.3.0, 1.2.1
>
>         Attachments: hbase-15038.patch
>
>
> Currently ExportSnapshot uses a single Configuration instance for both the source and destination FileSystem instances to use.  It should allow overriding properties for each filesystem connection separately.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)