[
https://issues.apache.org/jira/browse/CASSANDRA-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703765#comment-17703765
]
Andres de la Peña commented on CASSANDRA-18301:
-----------------------------------------------
{quote}
we still don't know which format implementation was used in the previous
version of Cassandra
{quote}
We sure know the major sstable version for the previous Cassandra version we
want to be downgradable to. Perhaps we should use the last known version for
that branch?
{quote}the user may want to enable other features while keep the old sstables
format version - after enabling other features but not bumping sstable format
version, the user is still able to go back. Without enabling other new
features, the user will not be able to evaluate a new version{quote}
The list of disabled features when one decides to stay on that kind of
"compatibility mode" would not be the full list of new features in the new
version, but only those that require a new sstable version. For example,
Cassandra 5.0 compatible with 4.0 would disable extended TTLs and SSTable
tries, but the new dynamic data masking would be enabled because it doesn't
require a new sstable format.
> 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
