Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 18 Jul 2012 21:33:36 +0000 (UTC)
From: "Robert Coli (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1967329126.71879.1342647216509.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1373717143.28422.1330443946878.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CASSANDRA-3974) Per-CF TTL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Coli updated CASSANDRA-3974:
-----------------------------------

    Attachment: cassandra.1.0.10.replaying.log.after.exception.during.drain.txt
    
> Per-CF TTL
> ----------
>
>                 Key: CASSANDRA-3974
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3974
>             Project: Cassandra
>          Issue Type: New Feature
>    Affects Versions: 1.2
>            Reporter: Jonathan Ellis
>            Assignee: Kirk True
>            Priority: Minor
>             Fix For: 1.2
>
>         Attachments: cassandra.1.0.10.replaying.log.after.exception.during.drain.txt, trunk-3974.txt, trunk-3974v2.txt, trunk-3974v3.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira