You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2021/03/09 18:34:00 UTC
[jira] [Commented] (CASSANDRA-16295) upgradesstables/scrub support
for 2.x sstables
[ https://issues.apache.org/jira/browse/CASSANDRA-16295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298246#comment-17298246 ]
Ekaterina Dimitrova commented on CASSANDRA-16295:
-------------------------------------------------
I feel there was a chain of confusion because of a test failure which turned a different issue.
At least with upgradesstables, I didn't find any issues on 3.0 or 3.11 during the testing of CASSANDRA-15897
> upgradesstables/scrub support for 2.x sstables
> ----------------------------------------------
>
> Key: CASSANDRA-16295
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16295
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Ekaterina Dimitrova
> Assignee: Andres de la Peña
> Priority: Normal
> Fix For: 3.11.x, 4.0-rc
>
>
> This support is important for 2.0/3.0 cluster or 3.0/4.0 cluster that can/might contain 2.x sstables.
> 4.0 supports versions down to {{ma}}, and 3.0 supports versions down to {{jb}} (3.0 and 2.0.1 correspondingly). So by the time you're on 4.0, you should have no 2.0 sstables either way, and this needs to be fixed for 3.11
>
> *NOTE: I just marked the ticket with both 3.11 and 4.0 rc versions even if the bug is presented only in 3.11 but to make it appear as a blocker on the 4.0 board!!*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org