[
https://issues.apache.org/jira/browse/PHOENIX-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294741#comment-15294741
]
Hudson commented on PHOENIX-2862:
---------------------------------
FAILURE: Integrated in Phoenix-master #1230 (See
[https://builds.apache.org/job/Phoenix-master/1230/])
Some phoenix-spark IT tests are broken after PHOENIX-2862 (ankitsinghal59: rev
b20cb245a4c3a7994eb3562a7855c9464f84f40d)
* phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexTool.java
* phoenix-core/src/main/java/org/apache/phoenix/util/SchemaUtil.java
> 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
> Affects Versions: 4.8.0
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
> Fix For: 4.8.0
>
> Attachments: PHOENIX-2862.patch, PHOENIX-2862_v4.patch,
> PHOENIX-2862_v5.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)
