Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 13 Feb 2013 19:04:13 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12631278.1360250959507.285633.1360782253993@arcas>
In-Reply-To: <JIRA.12631278.1360250959507@arcas>
References: <JIRA.12631278.1360250959507@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-5228) Track maximum ttl and use
 to expire entire sstables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13577829#comment-13577829 ] 

Jonathan Ellis edited comment on CASSANDRA-5228 at 2/13/13 7:03 PM:
--------------------------------------------------------------------

Hints is a different case; I'd rather re-code the delivery mechanism to operate sstable-at-a-time, than keep them around until the TTL expires (which is usually much, much longer than "until we deliver it").

You're right about wanting to track max ttl; edited.
                
      was (Author: jbellis):
    You're right.  Edited.
                  
> Track maximum ttl and use to expire entire sstables
> ---------------------------------------------------
>
>                 Key: CASSANDRA-5228
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5228
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Priority: Minor
>
> It would be nice to be able to throw away entire sstables worth of data when we know that it's all expired.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira