[
https://issues.apache.org/jira/browse/CASSANDRA-15897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281371#comment-17281371
]
Brandon Williams commented on CASSANDRA-15897:
----------------------------------------------
+1 on 3.0.
bq. Since 4.0 cannot even read the lb SSTables, do we need a check at all when
we drop compact storage or we would expect that there won't be already any that
old SSTables on a cluster with 4.0 nodes?
After CASSANDRA-16063, shouldn't it refuse to start if there are old sstables?
As far as 4.0 blocker goes, I do feel that we need all upgrade procedures
finalized, and compact storage would be one of them.
> Dropping compact storage with 2.1-sstables on disk make them unreadable
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-15897
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15897
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Marcus Eriksson
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0-beta
>
>
> Test reproducing:
> https://github.com/krummas/cassandra/commits/marcuse/dropcompactstorage
--
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
