phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4765) Add client and server side config property to enable rollback of splittable System Catalog if required
Date Wed, 21 Nov 2018 19:20:00 GMT

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

Thomas D'Silva updated PHOENIX-4765:
------------------------------------
    Attachment:     (was: PHOENIX-4765-v1.patch)

> 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
>         Attachments: PHOENIX-4765-v2-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
(v7.6.3#76005)

Mime
View raw message