phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3817) VerifyReplication using SQL
Date Thu, 17 Aug 2017 22:39:03 GMT

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

Andrew Purtell commented on PHOENIX-3817:
-----------------------------------------

If I do a replication of 10000 rows from T1 to T2, GOODROWS=10000. If I then delete the first
row from T2 with sqline, I'll get this in the hbase shell

{noformat}
9999 row(s) in 0.6430 seconds
{noformat}

Correct. I deleted one row.

VerifyReplication seems confused:

{noformat}
	org.apache.phoenix.mapreduce.VerifyReplicationTool$Verifier$Counter
		BADROWS=10000
		ONLY_IN_SOURCE_TABLE_ROWS=100
{noformat}

That's not right. We are only missing one row.

> 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)

Mime
View raw message