[
https://issues.apache.org/jira/browse/CASSANDRA-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-4391.
---------------------------------------
Resolution: Duplicate
Fix Version/s: (was: 1.2)
dupes CASSANDRA-3929
> add CF level 'count based ttl' option
> -------------------------------------
>
> Key: CASSANDRA-4391
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4391
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2
> Reporter: Dave Brosius
> Priority: Minor
>
> It would be useful to have a column family level based ttl for columns based
> on column count. This would be both lazy and sloppy, in that the only
> guarantee you received was that the latest n columns would not be deleted.
> When a compaction occurs, only up to n of the latest columns would be added
> to the new sstable for any particular key.
> So it is possible that old columns are removed out of order, but again, you
> can be sure that the latest n columns are preserved.
--
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
