nebari icon indicating copy to clipboard operation
nebari copied to clipboard

A pure Rust database implementation using an append-only B-Tree file format.

Results 26 nebari issues
Sort by recently updated
recently updated
newest added

Closes #58. **This TODO list is for the previous attempt at integrating Sediment before it was rewritten in December** - [ ] transaction log caching needs to be replaced with...

Nebari should expand it's testing suite to include fuzz testing. Personally I don't have any experience with it, but some pointers here: - [cargo-fuzz](https://crates.io/crates/cargo-fuzz) is commonly used for this task,...

help wanted

The current implementation of read-file caching isn't great -- it never closes any files. This is fine for now, but we'll eventually run into open-file limits. The read-files (and maybe...

enhancement

From Discord, @rrichardson discovered that the MemoryFile implementation is incredibly slower than the real-file based implementation, at least when consumed from BonsaiDb -- on the order of magnitude of 10...

bug

Currently, TreeFiles store blobs/chunks in the same file that nodes are written to. When compacting a database, all of the blobs that are alive must be transferred to the new...

enhancement

It occurred to me that one aspect of locking that many databases support is a way to lock multiple tables for read to ensure that none of them change while...

enhancement

- #35 - #40 - Consider allowing larger transaction payloads - Add atomic upgrade - `TransactionLog` should expose a new error when the log format is the old format. -...

enhancement

While fixing some edge cases in 9e799b9fe3e1b5378c88d73bd51ca80861279454, I thought of another edge case. I believe it's one that we should care about: Imagine if you roll a transaction back, the...

bug
enhancement

Bonsaidb is a wonderful DB. Can this implement internal branch support for a struct with the versioned tree? Thanks,

enhancement
help wanted
question