Get desktop application:
View/edit binary Protocol Buffers messages
Used in: , ,
The request did not have an error.
The requested key does not exist.
The request was sent to the wrong thread, which is not responsible for the key.
The request timed out.
The lattice type was not correctly specified or conflicted with an existing key.
This error is returned by the routing tier if no servers are in the cluster.
Used in:
Used in: , ,
The specified key.
The IPs of the set of servers responsible for this key.
uint32 count = 6;
A protobuf to represent an individual key, both for requests and responses.
The key name for this request/response.
Used in: ,
create bucket.
delete bucket
The function to trigger, can be name, http endpoint, etc.
The function to trigger, can be name, http endpoint, etc.
The function to trigger, can be name, http endpoint, etc.
The function to trigger, can be name, http endpoint, etc.
optional
Used in: ,
Used in:
CONDITION = 4;
The name of this function.
The serialized representation of this function.
A request to execute a pre-registered function a single time.
The name of the fucntion to execute.
the worker issuing internal call (optional)
A unique ID used to match asynchronous requests to responses.
the client address, used for synchronous requests.
the session ID generated by platform
internal field used for indicating the need of synchronizations between scheduler and coordinator
string response_key = 3;
Used in:
Used in:
The arguments to be passed into the function.
remote Get reponse
put notifying reponse
The function to trigger, can be name, http endpoint, etc.
Used in: , , ,
The request did not have an error.
The requested bucket/key does not exist, which are given by coordinator.
The remote servers have no (requested) data, which are given by remote KVS.
The value type does not match.
the bucket exists, which may be caused by bucket creation.
The request timed out.
A request to the routing tier to retrieve server addresses corresponding to individual keys.
The IP-port pair at which the client will await a response.
The names of the requested keys.
A unique ID used by the client to match asynchornous requests with responses.
A 1-to-1 response from the routing tier for individual KeyAddressRequests.
A batch of responses for individual keys.
An error reported by the routing tier. This should only ever be a timeout.
A unique ID used by the client to match asynchronous requests with responses.
A mapping from individual keys to the set of servers responsible for that key.
Used in:
The specified key.
The IPs of the set of servers responsible for this key.
The IP-port pair at which the client will await a response.
The names of the requested keys.
A unique ID used by the client to match asynchornous requests with responses.
A unique ID used by the client to match asynchronous requests with responses.
The IP-port pair at which the client will await a response.
The names of the requested keys.
A unique ID used by the client to match asynchornous requests with responses.
A batch of responses for individual keys.
An error reported by the routing tier.
A unique ID used by the client to match asynchronous requests with responses.
An individual GET or PUT request; each request can batch multiple keys.
The type of this request (see RequestType).
A list of KeyTuples batched in this request.
The IP-port pair at which the client is waiting for the server's response.
A client-specific ID used to match asynchronous requests with responses.
fetch remote data (tmp).
A response to a KeyRequest.
The type of response being sent back to the client (see RequestType).
The individual response pairs associated with this request. There is a 1-to-1 mapping between these and the KeyTuples in the corresponding KeyRequest.
The request_id specified in the corresponding KeyRequest. Used to associate asynchornous requests and responses.
Any errors associated with the whole request. Individual tuple errors are captured in the corresponding KeyTuple. This will only be set if the whole request times out.
A protobuf to represent an individual key, both for requests and responses.
Used in: ,
The key name for this request/response.
The lattice type for this key. Only required for server responses and PUT requests.
The error type specified by the server (see AnnaError).
The data associated with this key.
The number of server addresses the client is aware of for a particular key; used for DHT membership change optimization.
A boolean set by the server if the client's address_cache_size does not match the metadata stored by the server.
A message representing a pointer to a particular version of a particular key.
Used in: ,
The name of the key we are referencing.
A vector clock for the version of the key we are referencing.
A wrapper message for a list of KeyVersions.
The list of KeyVersion references.
Serialization of last-write wins lattices.
The last-writer wins timestamp associated with this data.
The actual data stored by this LWWValue.
Used in:
No lattice type specified
Last-writer wins lattice
Unordered set lattice
Single-key causal lattice
Multi-key causal lattice
Ordered-set lattice
Priority lattice
An individual multi-key causal lattice, along with its associated dependencies.
The vector clock associated with this particular key.
The mapping from keys to vector clocks for each of the direct causal dependencies this key has.
The set of potentially causally concurrent values for this key.
Used in: ,
Serialization of lowest-priority-wins lattices.
The priority associated with this data
The actual data stored by this PriorityValue
An enum to differentiate between different KVS requests.
Used in: ,
A default type to capture unspecified requests.
A request to retrieve data from the KVS.
A request to put data into the KVS.
Used in: ,
Serialization of unordered set lattices.
An unordered set of values in this lattice.
Serialization of a single-key causal lattice.
The vector clock for this key, which maps from unique client IDs to monotonically increasing integers.
The set of values associated with this causal value. There will only be more than one here if there are multiple causally concurrent updates.
An arbitrary set of strings; used for a variety of purposes across the system.
An unordered set of keys.
Used in:
hints for re-execution
Used in: ,
manage triggers