heed VS databricks-kube-operator

At Meilisearch we are currently trying to add a better error handling in heed v0.20, our LMDB key-value store wrapper. Unfortunately, when there are a lot of generics it can become harder to play with…

There are issues and pull requests but I advise you to look at the milli folder in the Meilisearch repository, it’s where all the logic is done. We extensively use RoaringBitmaps, heed the LMDB wrapper and grenad when indexing.

I’ll continue to introduce new features and new safety guards until v0.20.0. Can you tell me more about your project? Or is it private?

LMDB support multiple readers and one writer at the same time. It is ensured by the library. Note that LMDB is a key-value store. You can use the heed library which is the most maintained Rust wrapper.

Note that heed is ensuring that you are not trying to use transactions, databases and environments in the right way. I have added much more work in that regard in the important update that I am working on too!

I am currently working on exposing the new LMDB encryption feature from heed the safe LMDB wrapper with the help of the Cryptography community.

Have you considered heed or even sanakirja?

rkv hasn't been updated for a while. I recommend using heed - https://docs.rs/heed

For wrappers around LMBD, I'd recommend RKV or Heed https://github.com/mozilla/rkv https://github.com/Kerollmops/heed

Here's another example of a custom rust operator, https://github.com/mach-kernel/databricks-kube-operator

Written by a co-worker to help manage our databricks projects across clusters. Works wonderfully!!

So I used kube-rs and came up with this: https://github.com/mach-kernel/databricks-kube-operator