mirror of
https://github.com/scylladb/scylladb.git
synced 2026-04-27 11:55:15 +00:00
503d4f014c
Currently, when a max purgeable timestamp is computed, there is no information where it comes from and how the value was obtained. Take compaction, if there are memtables or other uncompacting sstables possibly shadowing data, the timestamp is decreased to ensure a tombstone is not purged but the caller does not know what that the timestamp has its value. In this patch, we extend the return type of max_purgeable_fn to contain not only a timestamp but also an information on how it was computed. This information will be required to collect statistics on tombstone purge failures due to overlapping memtables/uncompacting sstables that come later in the series.