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

Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/01/04 11:24:40 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15080947#comment-15080947 ] 

Hudson commented on HBASE-15038:
--------------------------------

FAILURE: Integrated in HBase-1.3 #478 (See [https://builds.apache.org/job/HBase-1.3/478/])
HBASE-15038 ExportSnapshot should support separate configs for source (garyh: rev bb744b4090168cce95ab59c58a44722683130477)
* hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java


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