[
https://issues.apache.org/jira/browse/PHOENIX-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273164#comment-15273164
]
Samarth Jain commented on PHOENIX-2862:
---------------------------------------
bq. It seems like users need to have a config now on the server side to enable
system table upgrade to namespace
Yes , as system tables are accessed directly with the absolute name so if they
are migrated to namespace and client/server doesn't know about it, then they
cannot access them by using table name SYSTEM[.](as they should use SYSTEM[:])
This is rather an odd way of telling the clients that the system tables have
been upgraded to use namespace feature. I would rather advocate that users
should update the system tables to name spaces only when all the clients
connecting to the cluster are new clients. Considering this is a one off case
and that you already have a manual command line way of providing this upgrade,
I don't think this kind of check is necessary.
> 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)
