Get desktop application:
View/edit binary Protocol Buffers messages
Put puts the given key into the key-value store. A put request increments the revision of the key-value store and generates one event in the event history.
key is the key, in bytes, to put into the key-value store.
value is the value, in bytes, to associate with the key in the key-value store.
lease is the lease ID to associate with the key in the key-value store. A lease value of 0 indicates no lease.
If prev_kv is set, etcd gets the previous key-value pair before changing it. The previous key-value pair will be returned in the put response.
If ignore_value is set, etcd updates the key using its current value. Returns an error if the key does not exist.
If ignore_lease is set, etcd updates the key using its current lease. Returns an error if the key does not exist.
if prev_kv is set in the request, the previous key-value pair will be returned.
Range gets the keys in the range from the key-value store.
key is the first key for the range. If range_end is not given, the request only looks up key.
range_end is the upper bound on the requested range [key, range_end). If range_end is '\0', the range is all keys >= key. If range_end is key plus one (e.g., "aa"+1 == "ab", "a\xff"+1 == "b"), then the range request gets all keys prefixed with key. If both key and range_end are '\0', then the range request returns all keys.
limit is a limit on the number of keys returned for the request. When limit is set to 0, it is treated as no limit.
revision is the point-in-time of the key-value store to use for the range. If revision is less or equal to zero, the range is over the newest key-value store. If the revision has been compacted, ErrCompacted is returned as a response.
sort_order is the order for returned sorted results.
sort_target is the key-value field to use for sorting.
serializable sets the range request to use serializable member-local reads. Range requests are linearizable by default; linearizable requests have higher latency and lower throughput than serializable requests but reflect the current consensus of the cluster. For better performance, in exchange for possible stale reads, a serializable range request is served locally without needing to reach consensus with other nodes in the cluster.
keys_only when set returns only the keys and not the values.
count_only when set returns only the count of the keys in the range.
min_mod_revision is the lower bound for returned key mod revisions; all keys with lesser mod revisions will be filtered away.
max_mod_revision is the upper bound for returned key mod revisions; all keys with greater mod revisions will be filtered away.
min_create_revision is the lower bound for returned key create revisions; all keys with lesser create revisions will be filtered away.
max_create_revision is the upper bound for returned key create revisions; all keys with greater create revisions will be filtered away.
kvs is the list of key-value pairs matched by the range request. kvs is empty when count is requested.
more indicates if there are more keys to return in the requested range.
count is set to the number of keys within the range when requested.
Used in: ,
key is the key in bytes. An empty key is not allowed.
create_revision is the revision of last creation on this key.
mod_revision is the revision of last modification on this key.
version is the version of the key. A deletion resets the version to zero and any modification of the key increases its version.
value is the value held by the key, in bytes.
lease is the ID of the lease that attached to key. When the attached lease expires, the key will be deleted. If lease is 0, then no lease is attached to the key.
Used in:
default, no sorting
lowest target value first
highest target value first
Used in:
Used in: ,
cluster_id is the ID of the cluster which sent the response.
member_id is the ID of the member which sent the response.
revision is the key-value store revision when the request was applied. For watch progress responses, the header.revision indicates progress. All future events recieved in this stream are guaranteed to have a higher revision number than the header.revision number.
raft_term is the raft term when the request was applied.