[
https://issues.apache.org/jira/browse/CASSANDRA-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704151#comment-17704151
]
Jacek Lewandowski commented on CASSANDRA-18301:
-----------------------------------------------
You are right assuming we use the same configuration in yaml.
{quote}So, in general when a "compatibility mode" property is set we should
validate a startup that the rest of the config and its feature flags are
compatible with that choice. Does it makes sense?{quote}
yeah, that make sense to me
Let me summarize what I think:
We should have a separate option to control the sstables write format / version
(whether it is Cassandra version, exact version, some special value)
Do we all agree on that?
> 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
