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

Posted to dev@hbase.apache.org by "Chia-Ping Tsai (JIRA)" <ji...@apache.org> on 2017/08/30 06:14:00 UTC

[jira] [Resolved] (HBASE-15806) An endpoint-based export tool

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

Chia-Ping Tsai resolved HBASE-15806.
------------------------------------
    Resolution: Fixed

> An endpoint-based export tool
> -----------------------------
>
>                 Key: HBASE-15806
>                 URL: https://issues.apache.org/jira/browse/HBASE-15806
>             Project: HBase
>          Issue Type: New Feature
>          Components: Coprocessors, tooling
>    Affects Versions: 2.0.0
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: Experiment.png, HBASE-15806.patch, HBASE-15806.v10.patch, HBASE-15806.v10.patch, HBASE-15806.v11.patch, HBASE-15806-v1.patch, HBASE-15806-v2.patch, HBASE-15806-v3.patch, HBASE-15806.v4.patch, HBASE-15806.v5.patch, HBASE-15806.v6.patch, HBASE-15806.v7.patch, HBASE-15806.v8.patch, HBASE-15806.v9.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.4.14#64029)