-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can v2.0.1 work well with rocksdb 0.15.0? #42
Comments
Hey @ws4charlie, thanks for your interest in merk! As far as I know, updating to |
Sure. I'll do it but just by simply exposing an iterator accepting customized options. I'll let you know. |
Hi @mappum , Seems I can't push branch or create PR on Merk. Could you please check and see my revised source file mod.rs(test cases included) for range-based queries. Can you please let me know your decision for the release? Thanks a lot. |
@mappum Hi, when will the new version be released? |
Hi, I am sorry to bother you guys and put my question in here which might not be the correct place. I have been looking for a Merkleized KV store for my project and this Merk looks pretty nice to me. After looking into the latest release 'v2.0.1' for a while, I noticed that the Merk is still using rocksdb 0.14.0 instead of 0.15.0, which is now being used in develop branch of Merk.
The question is that can I simply point underlying rocksdb to 0.15.0 on a fork of Merk "v2.0.1" and assume that everything will be working fine if "cargo test" pass? The reason I wanted to upgrade to rocksdb 0.15.0 was that it provides both upper_bound and lower_bound options for iterator. I appreciate it if any of you guys could help me on this. Thanks a lot.
The text was updated successfully, but these errors were encountered: