[
https://issues.apache.org/jira/browse/PHOENIX-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340263#comment-15340263
]
Samarth Jain commented on PHOENIX-3010:
---------------------------------------
[~jamestaylor] - where will add this config?
Client side - not sure it will work. We would also need to upgrade clients with
this special code of handling major version mismatch.
Server side - we will need to update region servers with this new config along
with replacing the server coprocessor jars. Then looking at the client version
and at this config, server will possibly respond with a major version so that
the older client won't fail compatibility check (ugly).
> Allow optional rolling restart for major release
> -------------------------------------------------
>
> Key: PHOENIX-3010
> URL: https://issues.apache.org/jira/browse/PHOENIX-3010
> Project: Phoenix
> Issue Type: Improvement
> Reporter: James Taylor
> Assignee: Samarth Jain
>
> If the major version number of the client does not match the major version of
> the server, the client is not allowed to connect to the server. However,
> sometimes a major release may make breaking changes to features that are not
> being used by users. In that case, an older client (i.e. 4.x) would work fine
> against a new server (i.e. 5.0). We should have a config parameter, something
> like {{phoenix.connection.allowPriorMajorVersion}} that allows this
> connection to take place, but defaults to false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
