Add the FDB async driver. #1856
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Adds all the machinery to run FDB. - Update the connection options to be able to select drivers. - Update code to use the Driver interface depending on driver. - Update testing harness to be able to read a ServerConfig file.
calavera
force-pushed
the
foundationdb_async_driver
branch
from
872024f to
a97d600
Compare
3 tasks
They're required as FDB doesn't link clients statically.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
Replaces #1845 as an incremental approach to add a new driver to the state store.
What
Testing
Tests still rely on RocksDB as driver. There is an option to run the tests against FDB which is not operational yet. That's the next step for this PR.
Contribution Checklist
make fmtin the package directory.make fmtinserver/.