We have an application that stores session data in Cassandra. The session data needs to be deleted after, say, one hour of inactivity. The CASSANDRA-699 TTL update in 0.7 looks like it will work very well for that.
However, we have a few scenarios where some session data will be retrieved frequently, but not be updated at all. In that scenario we need to make sure that the TTL gets refreshed on each read. I'm currently handling this by rewriting the entire column with a new timestamp and TTL. That seems a bit inefficient. Sometimes the column data can be several megabytes in size, and the only things in the column that need to be updated are the timestamp and the TTL. Is there currently a way to just update the timestamp and TTL? If not, would it make sense to update the get method and the associated internal plumbing to allow for an optional TTL parameter? -Omer
