cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Hanna (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-3974) Per-CF TTL
Date Tue, 20 Nov 2012 19:51:00 GMT

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

Jeremy Hanna edited comment on CASSANDRA-3974 at 11/20/12 7:49 PM:
-------------------------------------------------------------------

So this isn't going into 1.2 because it didn't apply cleanly to trunk?  I'm confused why the
status is set to open and the target version is now set to 1.3.
                
      was (Author: jeromatron):
    So this isn't going into 1.2 because it didn't apply cleanly to trunk?  I'm confused why
the status is set to open and the target version is not set to 1.3.
                  
> 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.0 beta 1
>            Reporter: Jonathan Ellis
>            Assignee: Kirk True
>            Priority: Minor
>             Fix For: 1.3
>
>         Attachments: 3974-v8.txt, trunk-3974.txt, trunk-3974v2.txt, trunk-3974v3.txt,
trunk-3974v4.txt, trunk-3974v5.txt, trunk-3974v6.txt, trunk-3974v7.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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message