[
https://issues.apache.org/jira/browse/CASSANDRA-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281036#comment-13281036
]
Sylvain Lebresne commented on CASSANDRA-3974:
---------------------------------------------
I does indeed seem that removeDeleted is not called on that path. I don't know
if this show up as a bug though: columns shadowed by a row tombstone are
removed by QueryFilter.isRelevant, and column tombstones are removed before
being returned to the client. Yet, it would probably be cleaner to put
removeDeleted on every path, especially since I agree with Jonathan that it's
probably the right place to put the CF-TTL check.
Actually I think that if we make sure to put removeDeleted on every path, we
could probably make it the only method concerned with tombstone and remove
QueryFilter.isRelelevant for instance, which would clean things up. But we can
probably leave that to another ticket.
> Per-CF TTL
> ----------
>
> Key: CASSANDRA-3974
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3974
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Assignee: Kirk True
> Priority: Minor
> Fix For: 1.2
>
> Attachments: trunk-3974.txt
>
>
> Per-CF TTL would allow compaction optimizations ("drop an entire sstable's
> worth of expired data") that we can't do with per-column.
--
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
