cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Tolbert (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12434) Improve deletion_info in sstabledump to include calculated 'expires_at' based on local_delete_time + gc_grace_seconds
Date Thu, 11 Aug 2016 05:25:20 GMT

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

Andy Tolbert commented on CASSANDRA-12434:
------------------------------------------

Maybe 'expires_at' isn't the appropriate term since it could be conflated with TTLs, can probably
think of something better.

> Improve deletion_info in sstabledump to include calculated 'expires_at' based on local_delete_time
+ gc_grace_seconds
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12434
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12434
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Andy Tolbert
>            Priority: Minor
>
> It would be helpful if sstabledump included tombstone expiration time in {{deletion_info}}
output by calculating {{local_delete_time + gc_grace_seconds}}.  To do this it would need
access to the table schema to get at {{gc_grace_seconds}} which is currently not possible
until [CASSANDRA-9587].
> Example output, assuming gc_grace_seconds is 86400 (10 days):
> {code:javascript}
> { "name" : "data", "deletion_info" : { "marked_deleted" : "2016-07-01T18:00:06.800550Z",
"local_delete_time" : "2016-07-01T18:00:06Z", "expires_at": "2016-07-11T18:00:06Z" } }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message