[
https://issues.apache.org/jira/browse/CASSANDRA-15897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149449#comment-17149449
]
Alex Petrov commented on CASSANDRA-15897:
-----------------------------------------
I like the idea with {{COMPACT_STORAGE_DROPPED}} flag, but that won't work for
people who have already dropped them (however, disallowing dropping won't help
them, either). You also did mention it won't be retroactive.
I'm personally in favour of not allowing {{DROP COMPACT STORAGE}} unless all
tables are upgraded, since it's a bit simpler to maintain. Maybe, depending on
how [CASSANDRA-15811] is implemented, that can even be a node-local decision?
> 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
>
> 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
