You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Alex Araujo (JIRA)" <ji...@apache.org> on 2017/06/05 17:28:04 UTC
[jira] [Commented] (PHOENIX-3817) VerifyReplication using SQL
[ https://issues.apache.org/jira/browse/PHOENIX-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037249#comment-16037249 ]
Alex Araujo commented on PHOENIX-3817:
--------------------------------------
v1 patch that compares tables using optional SQL conditions. Mind reviewing [~jamestaylor]? ITs are passing locally.
Will also do a round of testing on secure clusters to make sure token auth works correctly.
> 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
> Attachments: PHOENIX-3817.v1.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.3.15#6346)