cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3974) Per-CF TTL
Date Sat, 21 Apr 2012 12:28:29 GMT


Jonathan Ellis commented on CASSANDRA-3974:

I mean, a CF ttl of X is useful only if it lets us reason that an sstable written more than
X seconds ago is entirely expired.  So... min? :)

Is describe caching the schema as in CASSANDRA-4052?

Agreed that if we want to allow altering CF ttl, keeping it separate from column ttl until
we need to check for expired-ness makes the most sense.
> 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