You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Chinmay Kulkarni (Jira)" <ji...@apache.org> on 2020/08/25 18:52:00 UTC

[jira] [Updated] (PHOENIX-6036) Introduce a new statement to rollback Splittable SYSTEM.CATALOG changes when phoenix.allow.system.catalog.rollback=true

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

Chinmay Kulkarni updated PHOENIX-6036:
--------------------------------------
    Priority: Critical  (was: Major)

> Introduce a new statement to rollback Splittable SYSTEM.CATALOG changes when phoenix.allow.system.catalog.rollback=true
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-6036
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6036
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 5.0.0, 4.15.0
>            Reporter: Chinmay Kulkarni
>            Priority: Critical
>             Fix For: 5.1.0, 4.16.0
>
>
> Setting phoenix.allow.system.catalog.rollback=true makes it possible for the user to rollback changes introduced via Splittable SYSTEM.CATALOG. We however, do not have any command  to do so and the operator is responsible for doing SYSTEM table surgeries via manual steps like UPSERT SELECT statements to move parent->child links, running all drop view commands queued in SYSTEM.TASK, etc. We should introduce a command to do this for the user automatically. 



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