cassandra-commits mailing list archives

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

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

Jonathan Ellis resolved CASSANDRA-2620.
---------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 1.0)

Makes sense.

> 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
>
> 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