cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stu Hood (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2620) Don't persist TTL for expiring columns
Date Mon, 09 May 2011 11:24:03 GMT

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

Stu Hood commented on CASSANDRA-2620:
-------------------------------------

bq. would make the upgrade of those that rely on it (I know at least one production system
that does) both painful and error prone. So I think I'm -1 on this.
How are they using the TTL, if I may ask? This just seems like buggy behavior to me, so the
usecase would have to be pretty hard to accomplish in another fashion for it to be worth keeping
the bug around.

> Don't persist TTL for expiring columns
> --------------------------------------
>
>                 Key: CASSANDRA-2620
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2620
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Stu Hood
>            Priority: Minor
>             Fix For: 1.0
>
>
> We persist both the TTL (5 seconds from now) and the localExpirationTime (the local time
at +5 seconds) for expiring columns, but the TTL is never used again, except when we return
expiring columns to clients.
> Rather than storing the TTL to return to clients, we could calculate a delta TTL value
by subtracting the current time from the localExpirationTime, and save 4 bytes on disk.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message