-
Notifications
You must be signed in to change notification settings - Fork 1
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
Max value version of eleveldb #2
base: master
Are you sure you want to change the base?
Conversation
…t attempt of using antidote_utils, not working 100% yet.
to make it more efficient
to match the new architecture proposed, making it ready to support othr backends.
of AntidoteDB, when a non existent type is passed.
…d range in get_ops method
that has the mac value of the VC as part of the key
This tests are not running yet, so the originals are still in place.
…ith the ones in the _SUITE
Congratulations. How well has this been tested? We cannot afford to add instability to the main branch at this late point.
|
The eunit tests cover simple cases and the interesting ones we found in the last weeks + 94% of the code. The code was also tested with 200 000 Proper random test cases, with no failures. This PR is for the master branch of this repo. Merging this code will have no impact in Antidote code. I will try the antidote_db without interfering with the main branch in Antidote, so there is nothing to worry. |
This first PR, contains the initial implementation of the elevledb version of antidote_db.
Here is an overview of the new architecture proposed:
More information of how this works, can be found in the README.