[
https://issues.apache.org/jira/browse/PHOENIX-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16695113#comment-16695113
]
ASF GitHub Bot commented on PHOENIX-4765:
-----------------------------------------
GitHub user twdsilva opened a pull request:
https://github.com/apache/phoenix/pull/406
PHOENIX-4765 Add client and server side config property to enable rol…
…lback of splittable System Catalog if required
@ChinmaySKulkarni can you please review. This PR adds a config that is
used to enable rollback of splittable SYSTEM.CATALOG if required. If the config
is true, we continue storing the parent table column metadata while creating a
view. We also block any add columns and while creating a view try to lock the
parent table to prevent conflicting concurrent changes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/twdsilva/phoenix PHOENIX-4765
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/phoenix/pull/406.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #406
----
commit 1e54c280355bbc29e73b463134ffc95792172e7b
Author: Thomas D'Silva <tdsilva@...>
Date: 2018-11-20T20:10:05Z
PHOENIX-4765 Add client and server side config property to enable rollback
of splittable System Catalog if required
----
> 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-v1.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)
