[
https://issues.apache.org/jira/browse/CASSANDRA-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648684#comment-17648684
]
T Jake Luciani commented on CASSANDRA-8928:
-------------------------------------------
[~claude] has written an initial
[PR|https://github.com/apache/cassandra/pull/2045] that supports downgrading
via an offline tool (like sstableupgrader) Following a similar approach
described in this comment.
It requires extending the same contract we have in place for major upgrades.
We support reading from the last major sstable version and we support
reading/writing to the previous MessagingService version.
With this PR we add the ability to Write SSTables in the prior major format
(though with a new format key which includes the major version it belongs to).
This will allow someone who wants to revert major versions a simpler path.
Just stop each node (w/ flush), run offline downgrader, then restart with
previous version.
This will require some new docs and also a sstable downgrade dtest as well.
Would it be ok to re-assign this ticket to Claude?
> Add downgradesstables
> ---------------------
>
> Key: CASSANDRA-8928
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8928
> Project: Cassandra
> Issue Type: New Feature
> Components: Legacy/Tools
> Reporter: Jeremy Hanna
> Assignee: Kaide Mu
> Priority: Low
> Labels: gsoc2016, mentor, remove-reopen
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
