I also agree: Some mechanism to expire rolling data would be really good if we can incorporate it. Using the existing client interface, deleting old data is very cumbersome.
We want to store lots of audit data in Cassandra, this will need to be expired eventually. Nodes should be able to do expiry locally without needing to talk to other nodes in the cluster. As we have a timestamp on everything anyway, can we not use that somehow? If we only ever append data rather than update it (or update it very rarely), can we somehow store timestamp ranges in each sstable file and then have the server know when it's time to expire one? I'm guessing here from my limited understanding of how Cassandra works. Mark
