[
https://issues.apache.org/jira/browse/PHOENIX-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129753#comment-16129753
]
Andrew Purtell commented on PHOENIX-3817:
-----------------------------------------
[~alexaraujo]
Example usage in the help string would be very helpful.
I used:
{noformat}
./bin/hbase --config conf.1 org.apache.phoenix.mapreduce.VerifyReplicationTool
-z localhost:2181:/hbase-1
-tz localhost:2181:/hbase-2
-t TEST
{noformat}
This seems weird but the tool appears to complete the comparison successfully?
{noformat}
2017-08-16 18:34:59,857 INFO [main] jdbc.PhoenixEmbeddedDriver$ConnectionInfo:
Trying to connect to a secure cluster as 2181 with keytab /hbase-1
2017-08-16 18:34:59,858 INFO [main] jdbc.PhoenixEmbeddedDriver$ConnectionInfo:
Successful login to secure cluster
{noformat}
This INFO level debug string is too chatty:
{noformat}
2017-08-16 18:35:00,047 INFO [main] query.ConnectionQueryServicesImpl:
.writeNewSplits(JobSubmitter.java:493)
org.apache.hadoop.mapreduce.JobSubmitter.writeSplits(JobSubmitter.java:510)
org.apache.hadoop.mapreduce.JobSubmitter.submitJobInternal(JobSubmitter.java:394)
org.apache.hadoop.mapreduce.Job$10.run(Job.java:1285)
org.apache.hadoop.mapreduce.Job$10.run(Job.java:1282)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.Subject.doAs(Subject.java:422)
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1614)
org.apache.hadoop.mapreduce.Job.submit(Job.java:1282)
org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1303)
org.apache.phoenix.mapreduce.VerifyReplicationTool.verify(VerifyReplicationTool.java:159)
org.apache.phoenix.mapreduce.VerifyReplicationTool.run(VerifyReplicationTool.java:153)
org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
org.apache.phoenix.mapreduce.VerifyReplicationTool.main(VerifyReplicationTool.java:280)
{noformat}
> VerifyReplication using SQL
> ---------------------------
>
> Key: PHOENIX-3817
> URL: https://issues.apache.org/jira/browse/PHOENIX-3817
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Alex Araujo
> Assignee: Alex Araujo
> Priority: Minor
> Fix For: 4.12.0
>
> Attachments: PHOENIX-3817.v1.patch, PHOENIX-3817.v2.patch,
> PHOENIX-3817.v3.patch, PHOENIX-3817.v4.patch
>
>
> Certain use cases may copy or replicate a subset of a table to a different
> table or cluster. For example, application topologies may map data for
> specific tenants to different peer clusters.
> It would be useful to have a Phoenix VerifyReplication tool that accepts an
> SQL query, a target table, and an optional target cluster. The tool would
> compare data returned by the query on the different tables and update various
> result counters (similar to HBase's VerifyReplication).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
