-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
feat: ADR-040: Implement BadgerDB backend #9848
Conversation
As this depends on #9573, I'm making it a draft for now and will rebase when that is merged. Also, not sure if more documentation is needed beyond godoc comments. |
83a1c60
to
4d24407
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to wait until the mem-db PR is reviewed and merged before reviewing RocksDB and BadgerDB variants. We can rebase on master
after it's merged.
@roysc can this be rebased. Then we can begin reviewing |
dabc06f
to
6304cc9
Compare
Rebased and ready for review |
Co-authored-by: Aleksandr Bezobchuk <alexanderbez@users.noreply.github.com>
save more versions, fewer values
Along with review follow-ups, I fixed the version manager initialization so it's not dependent on ordered input, and updated a test case to verify its behavior. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
@roysc could you update to master, this will allow the bot to merge the PR |
We can merge this, yes? |
Visit https://dashboard.github.orijtech.com?back=0&pr=9848&remote=false&repo=cosmos%2Fcosmos-sdk to see benchmark details. |
Description
Partially resolves: vulcanize#14
Implements a BadgerDB-based backend for the DB interface introduced by #9573 and specified by ADR-040. This uses Badger's "managed" mode for version management, and supports optimistically concurrent transactions (required one patch upstream to fix handling of write conflicts).
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change