[
https://issues.apache.org/jira/browse/CASSANDRA-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715810#comment-17715810
]
anis ben brahim commented on CASSANDRA-8928:
--------------------------------------------
>From our tests we have downgraded from the 4.0.9 to the 3.11.14. In our first
>quick tests we have noticed that the keyword bigV3 is problematic when
>cassandra 3 start. By renaming this keyword by "big" in sstable filenames,
>Cassandra successfully start. For this quick test as mentioned in the tickets,
>system keysapces are not downgradable for now as it contains new columns and
>new tables. As DDL are not allowed during the migration, restoring system
>keyspaces from backups make this downgrade tool working. We are currently try
>to figure out all the points from system keyspaces that make the downgrade
>process failed and try to find some workarounds.
> 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: Claude Warren
> Priority: Low
> Labels: remove-reopen
> Fix For: 5.x
>
>
> 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
