[
https://issues.apache.org/jira/browse/CASSANDRA-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278344#comment-13278344
]
Kirk True commented on CASSANDRA-3974:
--------------------------------------
On IRC Jonathan suggested to look at {{ColumnFamilyStore.removeDeleted}} and
{{PrecompactedRow.removeDeletedAndOldShards}}. However, at doesn't _appear_
that either of these are called during column reads so I can't rely on those to
filter out results sent back to the client.
The logic that I see for filtering out results sent to the client is in places
such as {{CassandraServer.thriftifyColumns}} via the
{{IColumn.isMarkedForDelete}} call. However, as stated previously, since an
{{IColumn}} doesn't internally store a {{CFMetaData}} object, we'd have to pass
one in. {{isMarkedForDelete}} is used in a lot of places, so it has a ripple
effect that causes a lot of changes.
Please advise.
> 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
