phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-4286) Create EXPORT SCHEMA command
Date Fri, 13 Oct 2017 05:53:02 GMT
Geoffrey Jacoby created PHOENIX-4286:
----------------------------------------

             Summary: Create EXPORT SCHEMA command
                 Key: PHOENIX-4286
                 URL: https://issues.apache.org/jira/browse/PHOENIX-4286
             Project: Phoenix
          Issue Type: New Feature
            Reporter: Geoffrey Jacoby


Phoenix takes in DDL statements and uses it to create metadata in the various SYSTEM tables.
There's currently no supported way to go in the opposite direction. 

This is particularly important in migration use cases. If schemas between two clusters are
already synchronized, migration of data is _relatively_ straightforward using either Phoenix
or HBase's MapReduce integration. Syncing metadata can much more complicated, particularly
if only a subset needs to be migrated. For example, an operator migrating a single tenant
from one cluster to another would want to also migrate any views or sequences owned by that
tenant.

This can be accomplished by treating SYSTEM tables as data tables and migrating subsets of
them but implementations will be relying on brittle low-level implementation details that
can and do change. 

Given an EXPORT command, this could be done at a much higher level -- you simply select the
DDL statements from the source cluster you need, and then run them on the target cluster.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message