phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Araujo (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3817) VerifyReplication using SQL
Date Mon, 19 Jun 2017 14:45:00 GMT


Alex Araujo commented on PHOENIX-3817:

bq. Just out of curiousity, would this patch give us the capability of writing to both the
data table and index table in one pass to build indexes during a bulk load?
The Multi* classes in this patch are for reading from multiple tables in the same job. We
can add a MultiTableOutputFormat to write to multiple tables. We use something similar in
our tenant management tools to move specific tenants to different clusters in one pass (read
multi-tenant table once and output to different tables).

> VerifyReplication using SQL
> ---------------------------
>                 Key: PHOENIX-3817
>                 URL:
>             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
> 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