[
https://issues.apache.org/jira/browse/CASSANDRA-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Eriksson updated CASSANDRA-16735:
----------------------------------------
Fix Version/s: (was: 4.0-rc)
(was: 3.11.x)
(was: 3.0.x)
3.11.11
3.0.25
Since Version: 3.0.23
Source Control Link:
https://github.com/apache/cassandra/commit/1d87da3f6fc0eca4e805238c19db16e6607b44a7
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
committed to 3.0 and merged all the way up to trunk, thanks!
> 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: 3.0.25, 3.11.11, 4.0-rc2
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
