cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2620) Don't persist TTL for expiring columns
Date Mon, 09 May 2011 13:27:03 GMT


Jonathan Ellis commented on CASSANDRA-2620:

Couldn't we omit the TTL on disk, but recompute it in CassandraServer when creating the Thrift
struct to maintain compatibility there?

> Don't persist TTL for expiring columns
> --------------------------------------
>                 Key: CASSANDRA-2620
>                 URL:
>             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:

View raw message