[
https://issues.apache.org/jira/browse/PHOENIX-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340275#comment-15340275
]
James Taylor commented on PHOENIX-3010:
---------------------------------------
It would be a client-side config that simply prevents the throwing of the
INCOMPATIBLE_CLIENT_SERVER_JAR by modifying this ConnectionQueryServicesImpl
code and MetaDataUtil.areClientAndServerCompatible():
{code}
private static boolean isCompatible(Long serverVersion) {
if (serverVersion == null) {
return false;
}
// TODO pass through if major version mismatch allowed
return MetaDataUtil.areClientAndServerCompatible(serverVersion);
}
{code}
> 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)
