Struct SstFileWriter 

pub struct SstFileWriter { /* private fields */ }

Writes a standalone SSTable file that a running crate::Db can bulk-ingest via crate::Db::ingest_external_files.

Keys must be supplied in strictly ascending user-key order - duplicates and out-of-order keys are rejected with an error. Every entry is written with a placeholder sequence number of 0; the real sequence number is assigned by the engine when the file is ingested.

Implementations

impl SstFileWriter

pub fn create<P: AsRef<Path>>(path: P, opts: &Options) -> Result<Self>

Create a new SSTable file at path. The file is overwritten if it already exists. The writer borrows block_size, bloom_bits_per_key, and compression from opts after validating the option invariants.

pub fn put(&mut self, key: &[u8], value: &[u8]) -> Result<()>

Append a (key, value) pair to the default column family. key must be strictly greater than every previously added key.

pub fn delete(&mut self, key: &[u8]) -> Result<()>

Append a deletion tombstone for key in the default column family.

pub fn put_cf( &mut self, cf: &ColumnFamilyHandle, key: &[u8], value: &[u8], ) -> Result<()>

Append a (key, value) pair scoped to column family cf. Keys across CFs must still arrive in strictly ascending order (by prefixed bytes).

pub fn delete_cf(&mut self, cf: &ColumnFamilyHandle, key: &[u8]) -> Result<()>

Append a deletion tombstone scoped to column family cf.

pub fn finish(self) -> Result<SstFileMeta>

Finalize the file. Errors if no entries were written - an empty ingest file is almost certainly a bug and would be rejected at ingest time anyway.