[
https://issues.apache.org/jira/browse/CASSANDRA-19012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784685#comment-17784685
]
Berenguer Blasi commented on CASSANDRA-19012:
---------------------------------------------
I'm not sure if 18300 not being a 5.0 blocker is entirely reasonable as for
these testing implications i.e. In 18300 it should be decided if we _double_
the test matrix to test fully both formats, if we only do a single full both
formats run when approaching the release, which is the preferred method for
nodes to decide how to move forward onto newer formats/features, etc.
Answering your question I think it's best to open a new Jira. That would mean
changing circle files, maybe we want to do the same for Tries,... looks like
there's enough meat in there for it's own ticket and then we can target/discuss
that for 5.0 independent of 18300 if we choose so.
> 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: [email protected]
For additional commands, e-mail: [email protected]
