Disable database migration code on unsupported platforms or if the nobolt tag is present #37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently,
raft-boltdb
does not compile for unsupported architectures such as RISC-V because of its dependency on the unmaintainedgithub.com/boltdb/bolt
library. It appears the only reason that dependency exists is to be able to migrate v1 databases to v2, but it's not needed for this package to work.This PR moves the migration code and its associated unit tests to separate files and uses build tags to only build those files if the platform is supported by bolt and the
nobolt
tag is not set.Here are the results of running tests on this PR:
And on
riscv64
:Fixes #27