[
https://issues.apache.org/jira/browse/CASSANDRA-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703982#comment-17703982
]
Jacek Lewandowski commented on CASSANDRA-18301:
-----------------------------------------------
CEP-17 made the formats configurable. In particular, when we have a situation
where someone upgrades 5.0 to 6.0, 5.0 supports both big and bti formats - it
is not only about version, but also the type of the format. Saying that we want
to be compatible in 6.0 with 5.0 does not tell us much about which format to
choose. That's why I think that we should be explicit.
Though, the format could be selected as say "compatible" which could mean that
we select the format and version (note that, not only the version) by
examining the existing sstables, in particular - selecting the format and
version of the newest sstable found in the storage. That should also make the
system fail to start if that format/version is not supported for writing.
I'm just saying that I'm rather -1 on configuring the storage so that sstables
should be compatible with exact Cassandra version. If we don't want to be that
explicit, I'm still thinking that we should rather say something like
{{compatible}}, {{oldest_supported}}, {{newest_supported}}.
> 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: [email protected]
For additional commands, e-mail: [email protected]
