-
Notifications
You must be signed in to change notification settings - Fork 112
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
parachain/disputes: dispute coordinator backend #3344
parachain/disputes: dispute coordinator backend #3344
Conversation
7591e26
to
e8a5787
Compare
6b71e22
to
178c903
Compare
985cf97
to
cb3c834
Compare
9dc5a20
to
7cab038
Compare
e4e82d7
to
599c163
Compare
599c163
to
9aa4e94
Compare
593d728
to
ace8c36
Compare
83d8580
to
65dfe4c
Compare
1df6fa6
to
5bb1f74
Compare
You're right, but AFAIK you can use the pebble's Batcher which could replace the current badger transactions, more exactly the IndexedBatcher (https://github.com/cockroachdb/pebble/blob/master/batch.go), basically you can aggregate operations and commit or reset them |
hmm, that's interesting. I had come across this old issue cockroachdb/pebble#581. In their readme, they suggest rocksDB for transactions as well. I'm gonna have to go through it, but for now I'd like to continue with the integration tests. How about we revisit this at a later stage? |
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.
some remaining comments, but lgtm
d2c06da
to
7c80681
Compare
c0eb8a8
to
15643f9
Compare
7c80681
to
75c4eef
Compare
232f34e
into
feat/k/disputes-coordinator
We still need to do the pebbleDB implementation. I'll pick it up in the end. |
Changes
Implements backend for disputes-coordinator.
Parity's implementation:
https://github.com/paritytech/polkadot/blob/master/node/core/dispute-coordinator/src/backend.rs
https://github.com/paritytech/polkadot/tree/master/node/core/dispute-coordinator/src/db
Issues
#3302
Primary Reviewer
@kishansagathiya