cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Vorona (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3974) Per-CF TTL
Date Sun, 01 Apr 2012 20:02:27 GMT

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

Aleksey Vorona commented on CASSANDRA-3974:
-------------------------------------------

Copying real life use cases which need this feature from the older bug ( CASSANDRA-3077 ):

1. I want one of my CFs not to store any data older than two months. It is a "notifications"
CF which is of no interest to user past certain point in time.
Currently I am setting TTL with each insert in the CF, but since it is a constant it makes
sense to me to have it configured in CF definition to apply automatically to all rows in the
CF.

2. Default TTL would be very helpfull in Map/Reduce scenarios where you dont have direct control
of TTL (IE: hive)
                
> Per-CF TTL
> ----------
>
>                 Key: CASSANDRA-3974
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3974
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Jonathan Ellis
>            Assignee: Kirk True
>            Priority: Minor
>             Fix For: 1.2
>
>
> 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

        

Mime
View raw message