phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-2862) Do client server compatibility checks before upgrading system tables
Date Fri, 06 May 2016 17:13:13 GMT


James Taylor commented on PHOENIX-2862:

I see - thanks for the pointers. I think the way you're doing it is fine, then, but why is
there a server-side config for isSystemTablesMapped? I'd expect on the server side that you'd
just check for the existence of SYSTEM.CATALOG table in the SYSTEM namespace. Putting extra
burden on the user to set this config doesn't seem ideal to me.

> Do client server compatibility checks before upgrading system tables
> --------------------------------------------------------------------
>                 Key: PHOENIX-2862
>                 URL:
>             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
> 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

View raw message