phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chinmay Kulkarni (Jira)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-6035) Extend phoenix.allow.system.catalog.rollback to completely rollback changes introduced by Splittable SYSTEM.CATALOG
Date Wed, 22 Jul 2020 21:37:00 GMT
Chinmay Kulkarni created PHOENIX-6035:
-----------------------------------------

             Summary: Extend phoenix.allow.system.catalog.rollback to completely rollback
changes introduced by Splittable SYSTEM.CATALOG
                 Key: PHOENIX-6035
                 URL: https://issues.apache.org/jira/browse/PHOENIX-6035
             Project: Phoenix
          Issue Type: Improvement
            Reporter: Chinmay Kulkarni


Currently, phoenix.allow.system.catalog.rollback=true just makes sure that SYSTEM.CATALOG
does not split and continues writing parent column metadata with view metadata. Clients that
want 4.15/4.x features without needing SYSTEM.CATALOG to be splittable can already just provide
phoenix.system.catalog.splittable=false. We should extend the phoenix.allow.system.catalog.rollback
config so that when it is true, it will include the following:

* Continue writing parent->child links to SYSTEM.CATALOG instead of using SYSTEM.CHILD_LINK
* Not use SYSTEM.TASK for dropping child views but directly issue the drop view commands since
SYSTEM.CATALOG is on a single region anyways
* In the upgrade path for 4.16, if this config is on, we will have to reliably also do the
following:
# Move all parent->child links from SYSTEM.CHILD_LINK to SYSTEM.CATALOG
# Clean the SYSTEM.TASK table and execute all unscheduled tasks



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message