[
https://issues.apache.org/jira/browse/CASSANDRA-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328361#comment-15328361
]
Jeremy Hanna commented on CASSANDRA-8928:
-----------------------------------------
The primary use case for downgrading sstables is to abort an upgrade. So for
example, if you're on 2.1 and want to go to 2.2 or 3.x, the upgrade plan often
includes a contingency plan to abort and revert back to the older version,
including preserving data written while in the upgraded version. While
backwards compatible streaming (CASSANDRA-8110) is helpful in other scenarios,
it wouldn't help for that use case.
> Add downgradesstables
> ---------------------
>
> Key: CASSANDRA-8928
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8928
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Reporter: Jeremy Hanna
> Assignee: Kaide Mu
> Priority: Minor
> Labels: gsoc2016, mentor
>
> As mentioned in other places such as CASSANDRA-8047 and in the wild,
> sometimes you need to go back. A downgrade sstables utility would be nice
> for a lot of reasons and I don't know that supporting going back to the
> previous major version format would be too much code since we already support
> reading the previous version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
