[
https://issues.apache.org/jira/browse/CASSANDRA-18300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782889#comment-17782889
]
Maxwell Guo commented on CASSANDRA-18300:
-----------------------------------------
[~jlewandowski]Do we need to open a ticket just for the downgrade ability for
system schema ? Because with the upgrade of version ,the schema of system table
has alos change.I think we may need to discuss in detail the handling of these
tables before the first successful downgrade.
As CASSANDRA-18934 described, the commitlog's data for upper version cassandra
's system tables, may contains the useless data for downgrade version cassandra
that may affect successful downgrade.
I think we can dismantle this matter carefully and solve it one by one
accordingly.
> Support robust downgradability
> ------------------------------
>
> Key: CASSANDRA-18300
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18300
> Project: Cassandra
> Issue Type: Epic
> Reporter: Jacek Lewandowski
> Priority: Normal
>
> List of all the issues, improvements, assumptions and other things we should
> consider to allow the user to go back to the previous version without
> problems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
