[
https://issues.apache.org/jira/browse/CASSANDRA-16920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-16920:
------------------------------------------
Fix Version/s: 4.1
Since Version: 4.x
Source Control Link:
https://github.com/apache/cassandra/commit/e86ae7fbe52c95747d69f7d78b6da6fbd34bd48d
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Make creation timestamp consistent for all tables of a snapshot
> ---------------------------------------------------------------
>
> Key: CASSANDRA-16920
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16920
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Snapshots
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.1
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This mostly affects listsnapshots command as well as removal of a snapshot
> when it is on TTL.
> Currently, there is not the same timestamp for "created_at" field in
> listsnapshots output so what might happen when TTL deletion kicks in is that
> only part of tables might be removed because other tables do not have to make
> it into that TTL threshold but they will be removed on the next
> SnapshotManager's removal round.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
