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 2019/12/21 00:53:03 UTC
[jira] [Closed] (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 ]
Chinmay Kulkarni closed PHOENIX-4765.
-------------------------------------
Bulk closing Jiras for the 4.15.0 release.
> 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
> Assignee: Thomas D'Silva
> Priority: Blocker
> Fix For: 4.15.0, 5.1.0
>
> Attachments: PHOENIX-4765-v2-4.x-HBase-1.3.patch, PHOENIX-4765-v2.patch
>
>
> After the server has been upgraded we will have a client and server side config property that will allow us to rollback the upgrade if required. This config will:
> 1. Continue storing parent column metadata along with a child view
> 2. Disallow metadata changes to a base table that require being propagated to child views.
> 3. Prevent SYSTEM.CATALOG from splitting.
> 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 as part of PHOENIX-3534.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)