hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "HBase Review Board (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3013) Tool to verify data in two clusters
Date Thu, 28 Oct 2010 23:53:23 GMT

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

HBase Review Board commented on HBASE-3013:
-------------------------------------------

Message from: stack@duboce.net

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://review.cloudera.org/r/1111/#review1693
-----------------------------------------------------------

Ship it!


Excellent.  Minor items to address on commit.  So, is this new fancy tool doc'd in replication
notes?  I think it kinda critical.  Would suggest opening a doc issue against 0.90 to mention
presence of this tool in the replication chapter.... if only a sentence.


/trunk/src/main/java/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.java
<http://review.cloudera.org/r/1111/#comment5603>

    Missing '<p>' here?



/trunk/src/main/java/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.java
<http://review.cloudera.org/r/1111/#comment5602>

    Space around the '+'



/trunk/src/main/java/org/apache/hadoop/hbase/mapreduce/replication/VerifyReplication.java
<http://review.cloudera.org/r/1111/#comment5604>

    Put this in Result?


- stack





> Tool to verify data in two clusters
> -----------------------------------
>
>                 Key: HBASE-3013
>                 URL: https://issues.apache.org/jira/browse/HBASE-3013
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>             Fix For: 0.90.0
>
>
> It would be useful to have a tool to easily compare the data between tables in different
clusters, at least to make sure that replication is working correctly. I'm thinking of building
that inside CopyTable, kind of an option à là --verify that could be run independently or
after the copy (or not at all). The fact that we can already pass start/stop times is pretty
useful too when you don't want to check the whole tables, do incremental verifications, etc.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message