You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Thanh (Jira)" <ji...@apache.org> on 2020/06/18 13:02:00 UTC
[jira] [Created] (CASSANDRA-15882) sstablemetadata should show
tombstone timestamp not just the local drop time
Thanh created CASSANDRA-15882:
---------------------------------
Summary: sstablemetadata should show tombstone timestamp not just the local drop time
Key: CASSANDRA-15882
URL: https://issues.apache.org/jira/browse/CASSANDRA-15882
Project: Cassandra
Issue Type: Improvement
Reporter: Thanh
issue/request:
sstablemetadata should show tombstone timestamp not just the local drop time
I'm not sure what all versions this exists in but the sstablemetadata tombstone "drop time" only just shows the local delete time of the tombstones. What's more important (what the tombstone expiration time depends on) is the tombstone writetime (tombstone timestamp). It's possible to, and a surprising number of users have done this, write a tombstone with a timetamp in the future (by doing "DELETE...USING TIMESTAMP <future_timestamp>"). When this happens, the tombstone hangs around in sstables for a lot longer than users expect because
{code:java}
tombstone_expiration_time = gc_grace_seconds + tombstone_timestamp{code}
NOT
{code:java}
tombstone_expiration_time = gc_grace_seconds + tombstone_local_delete_time{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org