[
https://issues.apache.org/jira/browse/CASSANDRA-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-6570.
---------------------------------------
Resolution: Later
Fix Version/s: (was: 2.1)
Assignee: (was: Marcus Eriksson)
... Aleksey points out that besides 2PC, CASSANDRA-6504 and CASSANDRA-5202 and
possibly others are deal breakers here.
Looks like it's too late to retrofit this into 2.1, but we'll make it a goal
for 3.0.
> 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
>
> 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)
