You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2022/06/07 18:40:00 UTC

[jira] [Updated] (PHOENIX-3817) VerifyReplication using SQL

     [ https://issues.apache.org/jira/browse/PHOENIX-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey Jacoby updated PHOENIX-3817:
-------------------------------------
    Fix Version/s: 5.3.0
                       (was: 4.17.0)
                       (was: 5.2.0)
                       (was: 4.16.2)

> 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: 5.3.0
>
>         Attachments: PHOENIX-3817-final.patch, PHOENIX-3817-final2.patch, PHOENIX-3817.v1.patch, PHOENIX-3817.v2.patch, PHOENIX-3817.v3.patch, PHOENIX-3817.v4.patch, PHOENIX-3817.v5.patch, PHOENIX-3817.v6.patch, PHOENIX-3817.v7.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
(v8.20.7#820007)