rishavbhowmik / storage-engine-rust Goto Github PK

• Create sample storage files
• Copy sample file to temp_dir
• test write, read, delete repetitively and verify file states

Template unit tests and integration test with storage flows

Currently, if the 4 blocks have been written, the on reading 5th block (non existent block), the function read seeks read pointer outside the file bound, which is an illegal operation.

Expectation:

• maintain index of last block in the storage
• on request to read block index greater than max block index, return empty vector.

• write from buffer
• write from file

return array of block indexes used in order of data

So far we support creating for new storage file and initialisation of storage header and then read/write blocks. But now we need to open existing storage file, read storage header, search empty blocks and then read/write blocks.

ToDo

• implement Storage.get_storage_header - read data set using Storage.get_storage_header
• implement Storage.read_storage_block_headers - count total used blocks and update Storage.free_blocks for indexing empty blocks
• implement Storage::open - opens existing StorageFile - use Storage::open_file_writer with truncate false

  storage-engine-rust/src/storage/mod.rs

  Line 120 in a7302bb

  // TODO: Implement

• Atomic Lock
• Serve Reads
• Allocate blocks for writes
• Atomic Lock
• Write to allocated blocks
• Serve Delete requests
• Atomic Lock

Support Delete block operation

• set block data size to 0 and add block to empty blocks index
• set all data bytes to 0 if hard_delete set to true