Status: OUT
The SSTable format has no integrity or efficiency safeguards: entries carry no CRC or checksum, range scans bypass the sparse index and scan from file start, and the entry count header is trusted without verification — meaning corruption goes undetected, negative lookups are unnecessarily expensive, and truncated files produce silent data loss.
three independent gaps (integrity, index usage, header validation) leave the format defenseless
Depends on (SL): sstable-no-checksums, sstable-range-scan-no-index-skip, entry-count-header-never-verified