[
https://issues.apache.org/jira/browse/PHOENIX-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16539589#comment-16539589
]
ASF GitHub Bot commented on PHOENIX-3817:
-----------------------------------------
GitHub user akshita-malhotra opened a pull request:
https://github.com/apache/phoenix/pull/309
[Do Not Merge] PHOENIX-3817 Verify Replication using SQL conditions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/akshita-malhotra/phoenix Phoenix3817
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/phoenix/pull/309.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #309
----
commit abf570eac4f7678148d1498f6140b74fa61e1bd3
Author: Akshita Malhotra <akshita.malhotra@...>
Date: 2018-06-01T17:38:43Z
Verify Replication using SQL conditions
----
> VerifyReplication using SQL
> ---------------------------
>
> Key: PHOENIX-3817
> URL: https://issues.apache.org/jira/browse/PHOENIX-3817
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Alex Araujo
> Assignee: Akshita Malhotra
> Priority: Minor
> Fix For: 4.15.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
(v7.6.3#76005)
