-
Notifications
You must be signed in to change notification settings - Fork 224
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
Remove DQLITE_NEXT guard and unify with disk mode #671
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #671 +/- ##
==========================================
+ Coverage 77.56% 77.87% +0.30%
==========================================
Files 197 197
Lines 27638 27936 +298
Branches 5486 5520 +34
==========================================
+ Hits 21438 21754 +316
- Misses 4326 4356 +30
+ Partials 1874 1826 -48 ☔ View full report in Codecov by Sentry. |
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.
Looking very good Cole! Thanks for creating a different PR for these changes, it was much much easier to review. I left a lot of comments but 90% of them are about using constants :P and the rest are questions that I had.
96ed7c1
to
5c1f4de
Compare
This commit removes the DQLITE_NEXT build configuration. Code for the new disk mode that was previously guarded by `#ifdef DQLITE_NEXT` can instead be selected at run time by calling the new `dqlite_node_create_v2` function. At the raft level, this is supported by making the "format version" number a dynamic value instead of a compile-time constant and plumbing it around. Signed-off-by: Cole Miller <[email protected]>
Signed-off-by: Cole Miller <[email protected]>
5c1f4de
to
b4d705b
Compare
dd4bf48
to
0959b3d
Compare
Signed-off-by: Cole Miller <[email protected]>
0959b3d
to
b4057df
Compare
Signed-off-by: Cole Miller <[email protected]>
Signed-off-by: Cole Miller <[email protected]>
This is an experimental interface, but that doesn't mean it's frictionless to change it: go-dqlite is downstream of us and will have to be updated if we decide to change the signature. So let's leave some room to grow by taking a flags bitmask instead of a single bool. Signed-off-by: Cole Miller <[email protected]>
This lets us avoid breaking the go-dqlite build. Partially reverts commit 7cf8728. Signed-off-by: Cole Miller <[email protected]>
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.
Thanks for the changes to the public API, lgtm!
This reverts commit ad92843.
Signed-off-by: Cole Miller <[email protected]>
As discussed on MM I've pushed commits to remove the |
This PR removes the DQLITE_NEXT build configuration. Code for the new disk mode that was previously guarded by
#ifdef DQLITE_NEXT
can instead be selected at run time by calling the newdqlite_node_create_v2
function. At the raft level, this is supported by making the "format version" number a dynamic value instead of a compile-time constant and plumbing it around.Standalone version of the first part of #661, with the relevant review comments addressed (thanks @letFunny).
Signed-off-by: Cole Miller [email protected]