[ 
https://issues.apache.org/jira/browse/CASSANDRA-16295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304929#comment-17304929
 ] 

Alex Petrov commented on CASSANDRA-16295:
-----------------------------------------

I agree with your assessment of the situation [~e.dimitrova], there's no 
confusion. I also agree we can close the ticket since there's no issue here.

> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to