You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2021/06/11 19:14:00 UTC
[jira] [Commented] (CASSANDRA-16735) Adding columns via ALTER TABLE
can generate corrupt sstables
[ https://issues.apache.org/jira/browse/CASSANDRA-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361993#comment-17361993 ]
Ekaterina Dimitrova commented on CASSANDRA-16735:
-------------------------------------------------
[~marcuse], I am not familiar with these works but I am trying to filter the blockers for 4.0.0 Jira board and I saw this ticket. Reading your thoughts in the description, do you think we can revert 15899 to unblock 4.0.0?
> Adding columns via ALTER TABLE can generate corrupt sstables
> ------------------------------------------------------------
>
> Key: CASSANDRA-16735
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16735
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Local/SSTable
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 4.0-rc2, 3.0.x, 3.11.x, 4.0-rc
>
>
> This is similar to CASSANDRA-13004 and was caused by CASSANDRA-15899
> Basically the column placeholders introduced in 15899 can get read-repaired in to the memtable and later flushed to disk and in some cases this can conflict with the actual column (if the actual column is a collection for example) and cause CorruptSSTableExceptions.
> Fix is probably to just revert 15899, at least until if and when we find a solution that we can rely on. Will post that + test next week.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org