[
https://issues.apache.org/jira/browse/CASSANDRA-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868270#comment-13868270
]
Robert Coli commented on CASSANDRA-6570:
----------------------------------------
I +1 this idea of allowing people to safely upgrade a single node without
breaking backwards compatibility by writing new version SSTables, but is it
generally tractable? Won't many new major versions require the features in the
new SSTable versions?
> 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)
