cassandra-commits mailing list archives

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


Kirk True commented on CASSANDRA-3974:

There are a few pieces missing yet:

# The ability to alter a column family to change the default TTL option. Because I made the
change to use max(column TTL, CF TTL) at column mutate time, altering the column family default
TTL value will be "lost" on such columns.
# I'm fighting with Python to understand why 'DESCRIBE COLUMNFAMILY FOO' doesn't show the
new default TTL value. I made the change in the Python and Java layers to accept this new
option, but the describe fails to display it.
> 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