[
https://issues.apache.org/jira/browse/CASSANDRA-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13278414#comment-13278414
]
Kirk True edited comment on CASSANDRA-3974 at 5/17/12 11:52 PM:
----------------------------------------------------------------
In my case (inserting data and then calling {{list my_cf}} from the CLI), it
goes through the {{RangeSliceCommand}} path which doesn't end up calling
{{ColumnFamilyStorage.getColumnFamily}}. As such, the
expired-and-thus-should-be-ignored rows are still showing up.
was (Author: kirktrue):
In my case (inserting data and then calling {{list my_cf}} from the CLI}}),
it goes through the {{RangeSliceCommand}} path which doesn't end up calling
{{ColumnFamilyStorage.getColumnFamily}}. As such, the
expired-and-thus-should-be-ignored rows are still showing up.
> 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
