db: temporal KV client index_range API via gRPC #2189
Merged
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 implements temporal KV
index_range
API in gRPC client. The following interface changes become necessary:api::Service
toapi::Transaction
, as the inputapi::IndexRangeQuery
always needs to specify thetx_id
, i.e. the unique identifier of the enclosing db transactionapi::PaginatedTimestamps
, which is a sequence of timestamps paginated by using theapi::PaginatedSequence<T>
abstraction introduced in db: paginated sequence for temporal KV API #2186Extras
cmd
: addkv_index_range
command ingrpc_toolbox
to allow testing IndexRange KV RPC wrt Erigon3infra
: relax parameter type fromstd::unique_ptr<Stub>&
toStub&
inunary_rpc
function to allow easy usage of::remote::MockKVStub
in unit testsinfra
: add utility function translating::grpc::StatusCode
intoboost::system::error_code
infra
: add utility functions to produce gRPC status codes in unit testsrpc
: refactorengine_api_test
module to useDummyTransaction
test utility