hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15806) An endpoint-based export tool
Date Fri, 17 Jun 2016 18:29:05 GMT

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

Jerry He commented on HBASE-15806:
----------------------------------

{code}
+    Path file = new Path(request.getOutputPath(), "export-" + info.getEncodedName()); 
+    FileSystem fs = FileSystem.get(conf);
{code}
You want to get the fs from the path because it may be on another FS.

> An endpoint-based export tool
> -----------------------------
>
>                 Key: HBASE-15806
>                 URL: https://issues.apache.org/jira/browse/HBASE-15806
>             Project: HBase
>          Issue Type: New Feature
>    Affects Versions: 2.0.0
>            Reporter: ChiaPing Tsai
>            Assignee: ChiaPing Tsai
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: Experiment.png, HBASE-15806-v1.patch, HBASE-15806-v2.patch, HBASE-15806-v3.patch,
HBASE-15806.patch
>
>
> The time for exporting table can be reduced, if we use the endpoint technique to export
the hdfs files by the region server rather than by hbase client.
> In my experiments, the elapsed time of endpoint-based export can be less than half of
current export tool (enable the hdfs compression)
> But the shortcomings is we need to alter table for deploying the endpoint
> any comments about this? thanks



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

Mime
View raw message