[
https://issues.apache.org/jira/browse/HBASE-15806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16146088#comment-16146088
]
stack commented on HBASE-15806:
-------------------------------
Skimmed. +1. On commit, add note to hbase-endpoint/pom.xml on why the mapreduce
dependency; i.e. needed by this tool.
> 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.v10.patch, HBASE-15806.v10.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)
