[
https://issues.apache.org/jira/browse/CASSANDRA-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703651#comment-17703651
]
Andres de la Peña commented on CASSANDRA-18301:
-----------------------------------------------
I think that if we are going to use this to allow users to downgrade to a
previous major version, rather than a {{max_stable_version: nc}} yaml property
we could simply specify what Cassandra version we want to be able to downgrade
to.
The yaml property could look like:
{code:java}
# Minimum major Cassandra version it will be possible to directly downgrade to.
# If you stay downgradable to version 4.0 you won't be able to uses features a,
b, c...
downgradable_to_version: 4.0
{code}
Its documentation comment would say what features you are missing if you stay
on certain versions.
That way we wouldn’t bother users with sstable versions, which is an obscure
internal concept. Also, we can make more things than the sstable version depend
on that property. For example, the messaging version.
> Let the user select the sstable version to write
> ------------------------------------------------
>
> Key: CASSANDRA-18301
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18301
> Project: Cassandra
> Issue Type: New Feature
> Components: Local/Config, Local/SSTable
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
>
--
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
