db: state change stream and cache on generic KV API #2168
Merged
Conversation
This file contains 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
8 tasks
canepat
added
the
maintenance
lupin012
approved these changes
Jul 9, 2024
fix state change RPC lifecycle for cancellation expose back-off timeout utility
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.
This PR introduces a refactoring of state-change stream and cache on top of the generic
KVAPI now moved within thedbmodule, where generic here means capable of handling both in-process (a.k.a. direct) and out-of-process (i.e. gRPC) client-server setup.Both
StateChangeStreamandStateCachewere previously tied to the gRPC data types, now they're independent from such types and hence reusable also in the direct setup.Extras
CancellationTokensignal-slot ininframodule