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

Posted to dev@phoenix.apache.org by "Thomas D'Silva (JIRA)" <ji...@apache.org> on 2018/11/20 00:56:00 UTC

[jira] [Updated] (PHOENIX-4765) Add client and server side config property to enable rollback of splittable System Catalog if required

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

Thomas D'Silva updated PHOENIX-4765:
------------------------------------
    Summary: Add client and server side config property to enable rollback of splittable System Catalog if required  (was: Add server side config property to disallow metadata changes that require being propagated to children)

> Add client and server side config property to enable rollback of splittable System Catalog if required
> ------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4765
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4765
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Thomas D'Silva
>            Priority: Blocker
>
> After the server has been upgraded we will have a server side config property that will allow us to rollback the upgrade if required. This config will:
> 1. Disallow metadata changes to a base table that require being propagated to child views.
> If the client is older than the server we also disallow metadata changes to a base table with child views since we no longer lock the parent on the server side. This is handled on the client side in the new jar.
> 2. Prevent SYSTEM.CATALOG from splitting.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)