[
https://issues.apache.org/jira/browse/CASSANDRA-15897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150347#comment-17150347
]
Sylvain Lebresne commented on CASSANDRA-15897:
----------------------------------------------
I'll give a shot to the gossip route since that seems to win this popularity
contest, even if not by a great margin.
bq. And we might need a one-off tool/support in upgradesstables to convert
those 2.x sstables.
Yeah. I'll look at adding a flag to {{upgradesstables}}.
That said, I suspect there may be corner cases that we can't entirely handle.
For instance, if the user started adding/removing columns just after that
{{DROP COMPACT STORAGE}} and before figuring out that some tables couldn't be
read, then we might be in the dark. Does not mean we shouldn't try handling
those sstables in the simple case, but just to list a probable limitation.
> 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: [email protected]
For additional commands, e-mail: [email protected]
