[
https://issues.apache.org/jira/browse/HBASE-13639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216048#comment-15216048
]
Abhishek Soni commented on HBASE-13639:
---------------------------------------
I have tried to use this feature but I couldn't. Its usage detail still feels
incomplete. I can easily understand what this feature intends to do and its
internal procedure while doing so. But it would be great if we have an
elaborate usage information of this feature.
For ex., I have a table test1 in cluster1 with cf1:1,cf1:b & cf1,c columns and
another table with similar schema in cluster2 with name test2. What I
understood from this feature is that I can copy data from test1 table to test2.
But I am not sure how it should be done. Any document or simple steps for it
would be great help.
> SyncTable - rsync for HBase tables
> ----------------------------------
>
> Key: HBASE-13639
> URL: https://issues.apache.org/jira/browse/HBASE-13639
> Project: HBase
> Issue Type: New Feature
> Components: mapreduce, Operability, tooling
> Reporter: Dave Latham
> Assignee: Dave Latham
> Labels: tooling
> Fix For: 2.0.0, 0.98.14, 1.2.0
>
> Attachments: HBASE-13639-0.98-addendum-hadoop-1.patch,
> HBASE-13639-0.98.patch, HBASE-13639-v1.patch, HBASE-13639-v2.patch,
> HBASE-13639-v3-0.98.patch, HBASE-13639-v3.patch, HBASE-13639.patch
>
>
> Given HBase tables in remote clusters with similar but not identical data,
> efficiently update a target table such that the data in question is identical
> to a source table. Efficiency in this context means using far less network
> traffic than would be required to ship all the data from one cluster to the
> other. Takes inspiration from rsync.
> Design doc:
> https://docs.google.com/document/d/1-2c9kJEWNrXf5V4q_wBcoIXfdchN7Pxvxv1IO6PW0-U/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
