hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15806) An endpoint-based export tool
Date Sun, 02 Jul 2017 04:16:05 GMT

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

stack commented on HBASE-15806:
-------------------------------

Missing from release note is advantage of going this route. You have it in rb. Stick it in
release note too. Added a few comments on rb.



> 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: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: Experiment.png, HBASE-15806.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
>
>
> 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)

Mime
View raw message