[
https://issues.apache.org/jira/browse/CASSANDRA-15897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17235512#comment-17235512
]
Alex Petrov edited comment on CASSANDRA-15897 at 11/20/20, 3:30 PM:
--------------------------------------------------------------------
[~e.dimitrova] will we need a fix in 4.0, since 2.0 sstables can't be read by
4.0?
UPD: talked with [~e.dimitrova], and I was responding to a different question.
I was speaking only about 2.0 upgrades, but am generally +1 to do the proposed
"gossip" solution, assuming we're talking about mixed-mode 2.0/3.0 cluster or
3.0/4.0 cluster that can might contain 2.0 sstables.
was (Author: ifesdjeen):
[~e.dimitrova] will we need a fix in 4.0, since 2.0 sstables can't be read by
4.0?
> 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: Sylvain Lebresne
> Priority: Normal
> Fix For: 3.0.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
