Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Mon, 20 Jun 2016 23:39:58 +0000 (UTC)
From: "Mujtaba Chohan (JIRA)" <jira@apache.org>
To: dev@phoenix.incubator.apache.org
Message-ID: <JIRA.12981057.1466450892000.4591.1466465998145@Atlassian.JIRA>
In-Reply-To: <JIRA.12981057.1466450892000@Atlassian.JIRA>
References: <JIRA.12981057.1466450892000@Atlassian.JIRA> <JIRA.12981057.1466450892636@arcas>
Subject: [jira] [Commented] (PHOENIX-3010) Allow optional rolling restart
 for major release
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 20 Jun 2016 23:40:03 -0000


    [ https://issues.apache.org/jira/browse/PHOENIX-3010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340686#comment-15340686 ] 

Mujtaba Chohan commented on PHOENIX-3010:
-----------------------------------------

I was thinking of the scenario that someone upgraded server and then found that older client throwing incompatibility exception, now he'd need to set property cluster wide and restart again. Yes maybe a bit of corner case.

> 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)