[ https://issues.apache.org/jira/browse/CASSANDRA-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Eriksson updated CASSANDRA-16735: ---------------------------------------- Test and Documentation Plan: new test, cci run Status: Patch Available (was: Open) https://github.com/krummas/cassandra/commits/marcuse/16735-4.0.0 https://github.com/krummas/cassandra/commits/marcuse/16735-3.11 https://github.com/krummas/cassandra/commits/marcuse/16735 https://app.circleci.com/pipelines/github/krummas/cassandra?branch=marcuse%2F16735-4.0.0 https://app.circleci.com/pipelines/github/krummas/cassandra?branch=marcuse%2F16735-3.11 https://app.circleci.com/pipelines/github/krummas/cassandra?branch=marcuse%2F16735 > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org