memgraph/tests/simulation
gvolfing d06132cb33
Make ShardRequestManager work with futures (#588)
The communication between the ShardRequestManager and the RsmClient
used to be direct. In this PR this changes into a future-based
communication type. The RsmClient stores state about the currently
processed future (either read or write request) and exposes blocking
and non-blocking functionality to obtain the filled future. The
ShardRequestManager -for now- will send of the set of requests present
in the ExecutionState and block on each of them until the requests are
completed or the set of paginated responses(caused by, for example the
batch-limit in ScanAll) are ready for the next round.
2022-10-18 09:53:37 +02:00
..
trial_query_storage Transport prototype (#466) 2022-08-12 08:24:32 +02:00
basic_request.cpp Transport prototype (#466) 2022-08-12 08:24:32 +02:00
CMakeLists.txt Implement query engine client (#531) 2022-09-22 15:05:43 +02:00
common.hpp Implement query engine client (#531) 2022-09-22 15:05:43 +02:00
raft.cpp In memory shard map (#505) 2022-09-05 15:50:54 +03:00
shard_request_manager.cpp Update usage of Shard (#574) 2022-10-05 11:56:36 +02:00
shard_rsm.cpp Implement missing message handlers (#563) 2022-10-03 15:31:06 +02:00
sharded_map.cpp Make ShardRequestManager work with futures (#588) 2022-10-18 09:53:37 +02:00