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

One of the limitations of compacting files is that all of the version information is removed. Back when we had a few data accidents on CouchDB, this caused some of...

enhancement

When Nebari was originally being developed within the BonsaiDb repository, it wasn't that unreasonable to allow some of the code coverage of unit tests to be done by the integration...

enhancement
good first issue

We will want to be able to discard old entries in the transaction log. The safe way to do this will be to keep track of the last transactions that...

enhancement

After benchmarking scans, it's clear we're doing something that isn't optimal. Additionally, while reverse scanning isn't benchmarked, there is a `TODO` in the code to address optimizations that hadn't been...

enhancement

The current implementation of `get_multiple` and `scan` both take a key reader and key evaluator function. The reader is invoked for each key as it is found, and the result...

enhancement

The next release of Nebari will fundamentally change what Nebari is. Today, Nebari uses one-file-per-tree to store data in an append-only format. The `Roots` type uses an additional file to...