counting-bloom-trades-correctness-for-unneeded-capability

Status: IN

The counting Bloom filter pays 8x memory overhead and introduces false negatives through its removal operation for a capability (element deletion) that the primary use case — immutable SSTables — never needs, since SSTables are write-once and discarded whole during compaction.

Justifications

Counting bloom filter trades memory and correctness for deletion support SSTables don't require

Depends on (SL): cbf-8x-memory-vs-standard, cbf-remove-can-introduce-false-negatives, standard-bloom-suffices-for-immutable-sstables

JSON