Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 10 Jan 2014 20:31:50 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12688325.1389385795193.78746.1389385910962@arcas>
In-Reply-To: <JIRA.12688325.1389385795193@arcas>
References: <JIRA.12688325.1389385795193@arcas>
Subject: [jira] [Commented] (CASSANDRA-6570) Compatibility mode for 2.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-6570:
-------------------------------------------

(2.1 is an unusually good place to do this since AFAIK we haven't made any other incompatible changes, e.g. to schema propagation.)

> Compatibility mode for 2.1
> --------------------------
>
>                 Key: CASSANDRA-6570
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6570
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Marcus Eriksson
>             Fix For: 2.1
>
>
> Upgrading to a new major Cassandra release is a big commitment, because once on a new version you can't downgrade again because we write new-version sstables.
> Let's add an option to write old-version sstables so that users can try upgrading a single 2.1 RC node in a 2.0 cluster with the safety net of being able to back it out if anything goes wrong.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)