[
https://issues.apache.org/jira/browse/CASSANDRA-19012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784471#comment-17784471
]
Sam Tunnicliffe commented on CASSANDRA-19012:
---------------------------------------------
CASSANDRA-18300 is not a blocker for 5.0 (or any other specific version), which
is entirely reasonable. But as 5.0 _is_ going to produce {{oa}} sstables we
should probably enable the dtests to exercise them before we release it. Given
that this isn't really a concern about downgrading (just that we should be
covering the new format in regular & upgrade dtests) do we need another JIRA to
separate this specific issue out from 18300?
> It should be possible to read all supported versions of sstables regardless
> of the compatibility mode
> -----------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19012
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19012
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jacek Lewandowski
> Priority: Normal
> Fix For: 5.0.x
>
>
> Currently when the storage compatibility mode is set to 4, it set the current
> write version of the ssatable to the latest compatible with 4 (N). However,
> it additionally make new sstables (O) recognized as invalid, which is wrong.
> We should be able to read all versions of supported sstables regardless of
> the compatibility mode.
> We should also ensure testing the scenario when the node tries to stream the
> new format sstable (node with compat mode = upgrading) to a node with compat
> mode = 4 - the test should demonstrate that such streaming is refused
--
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
