[
https://issues.apache.org/jira/browse/CASSANDRA-16295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304520#comment-17304520
]
Ekaterina Dimitrova commented on CASSANDRA-16295:
-------------------------------------------------
Hi [~cscotta], there was a confusion in another ticket that upgradesstables is
broken in 3.11 and can't upgrade the old sstables which are not readable in
4.0. As a consequence, this can be an issue in a mixed version cluster. From
that perspective, it was agreed this issue to be handled before 4.0
As I took over CASSANDRA-15897 and did the testing I didn't see any issues with
upgradesstables.
To me it looked like a confusion due to test broken for different reasons.
Maybe [~adelapena], [~marcuse] or [~ifesdjeen] have something else in mind?
> 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: [email protected]
For additional commands, e-mail: [email protected]
