cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirk True (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3974) Per-CF TTL
Date Wed, 11 Apr 2012 21:57:24 GMT


Kirk True commented on CASSANDRA-3974:

I made changes to both {{UpdateStatement.addToMutation}} and {{ColumnFamily.addColumn}} to
use the larger of the column's TTL or the column family default TTL. I tested against the
{{cassandra-cli}} and {{cqlsh}} tools and both show the default TTL being used if none is

This is all to say that it _looks_ like both the Thrift and CQL paths are working as expected.
Perhaps it's high time I found the unit tests and added some...
> Per-CF TTL
> ----------
>                 Key: CASSANDRA-3974
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


View raw message