[
https://issues.apache.org/jira/browse/CASSANDRA-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161667#comment-13161667
]
Sylvain Lebresne commented on CASSANDRA-3538:
---------------------------------------------
It is definitively only an optimization, which LCR does use because it calls
Precompacted.removeDeletedAndOldShards, but not EchoedRow indeed. And even if
not a life changer, it's still an optimization. But I would be very fine with
putting this in trunk only if we don't want to take any risks.
> Remove columns shadowed by a deleted container even when we cannot purge
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-3538
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3538
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Trivial
> Fix For: 1.0.6
>
> Attachments: 3538.patch
>
>
> During compaction, if shouldPurge == false, we don't do anything with the
> column family. It is however ok to remove columns for with their container is
> deleted with a timestamp greater than their own.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
