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

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

GitHub user ankitsinghal opened a pull request:

    https://github.com/apache/phoenix/pull/167

    PHOENIX-2862 Do client server compatibility checks before upgrading system 
tables

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ankitsinghal/phoenix PHOENIX-2862

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/phoenix/pull/167.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 #167
    
----
commit 74f15dcfd4faba4c1aa1d4624fda407298460801
Author: Ankit Singhal <ankitsingha...@gmail.com>
Date:   2016-05-02T09:06:38Z

    PHOENIX-2862 Do client server compatibility checks before upgrading system 
tables

----


> Do client server compatibility checks before upgrading system tables
> --------------------------------------------------------------------
>
>                 Key: PHOENIX-2862
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2862
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Ankit Singhal
>            Assignee: Ankit Singhal
>             Fix For: 4.8.0
>
>         Attachments: PHOENIX-2862.patch
>
>
> currently , we allow upgrade of system tables to map to system namespace by 
> enabling "phoenix.schema.mapSystemTablesToNamespace" config (conjuction with 
> "phoenix.connection.isNamespaceMappingEnabled") 
> but we need to ensure following things whenever client connects with above 
> config:-
> 1. Server should be upgraded and check consistency of these properties 
> between client and server.
> 2. If above property does not exists but system:catalog exists, we should not 
> start creating system.catalog.
> 3. if old client connects, it should not create system.catalog again ignoring 
> the upgrade and start using it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to