[
https://issues.apache.org/jira/browse/CASSANDRA-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704480#comment-17704480
]
Jacek Lewandowski commented on CASSANDRA-18301:
-----------------------------------------------
There is separate ticket https://issues.apache.org/jira/browse/CASSANDRA-8110
which I think is aiming to address that problem. That is, it will not allow to
use the sstable format version higher than the lowest supported in the cluster.
That would work for upgrades where we have mixed clusters.
For the compatibility mode, which should be kept even after upgrade, so that
the user retains its ability to downgrade - it is up to the user to setup
Cassandra properly - it the user fails to setup compatibility mode on all the
nodes - it is a misconfiguration.
Though, we may do something to confirm that all the nodes use the same
configuration. I suppose that TCM can help there.
> 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
