Marcus Eriksson created CASSANDRA-15247:
-------------------------------------------
Summary: Avoid iterating the memtable contents when doing range
queries with `only_purge_repaired_tombstones` enabled
Key: CASSANDRA-15247
URL: https://issues.apache.org/jira/browse/CASSANDRA-15247
Project: Cassandra
Issue Type: Improvement
Components: Local/Memtable
Reporter: Marcus Eriksson
Currently we
[iterate|https://github.com/apache/cassandra/blob/893908e2dc1fe011e38c847395cb39be4ca53d89/src/java/org/apache/cassandra/db/Memtable.java#L360]
over the subrange of the memtable contents we are querying for to find the
oldest unrepaired tombstone, we could probably just track the oldest tombstone
globally for the memtable without any big drawbacks (we might include a few
more tombstones when doing the read).
Also noted that we use {{EncodingStats#minLocalDeletionTime}} without checking
for the {{DELETION_TIME_EPOCH}} value in a few places, this can make us include
too many expired tombstones during reads.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
