phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akshita Malhotra (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3817) VerifyReplication using SQL
Date Fri, 03 May 2019 22:15:00 GMT


Akshita Malhotra commented on PHOENIX-3817:

[~tdsilva] Sorry for the delay, I will commit it by early next week.

> VerifyReplication using SQL
> ---------------------------
>                 Key: PHOENIX-3817
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Alex Araujo
>            Assignee: Akshita Malhotra
>            Priority: Minor
>             Fix For: 4.15.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

View raw message