[ 
https://issues.apache.org/jira/browse/PHOENIX-4765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16699720#comment-16699720
 ] 

ASF GitHub Bot commented on PHOENIX-4765:
-----------------------------------------

Github user ChinmaySKulkarni commented on a diff in the pull request:

    https://github.com/apache/phoenix/pull/406#discussion_r236472049
  
    --- Diff: 
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java
 ---
    @@ -530,6 +530,10 @@ private static PName newPName(byte[] keyBuffer, int 
keyOffset, int keyLength) {
         private int maxIndexesPerTable;
         private boolean isTablesMappingEnabled;
     
    +    // this flag denotes that we will continue to write parent table 
column metadata while creating
    +    // a child view and also block metadata changes that were previously 
propagated to children
    +    // before 4.15, so that we can rollback the upgrade to 4.15 if required
    +    private boolean allowSystemCatalogRollback;
    --- End diff --
    
    Had a conversation offline with Thomas and the underlying point in my 
comment above is already being addressed. Thanks @twdsilva.


> 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-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
(v7.6.3#76005)

Reply via email to