You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Txn API only supports comparisons on single keys. However, comparisons on ranges that check whether all keys match the comparison target are useful for implementing higher-level functionality over etcd.
Disconnected linearized reads would use range comparisons to check for leased keys on a range before deleting a range:
The protocol change would add a range_end field to the Compare protobuf message:
messageCompare {
...
oneoftarget_union {
// version is the version of the given keyint64version=4;
// create_revision is the creation revision of the given keyint64create_revision=5;
// mod_revision is the last modified revision of the given key.int64mod_revision=6;
// value is the value of the given key, in bytes.bytesvalue=7;
}
bytesrange_end=8;
}
The text was updated successfully, but these errors were encountered:
Currently the Txn API only supports comparisons on single keys. However, comparisons on ranges that check whether all keys match the comparison target are useful for implementing higher-level functionality over etcd.
Disconnected linearized reads would use range comparisons to check for leased keys on a range before deleting a range:
STM could be extended to support key intervals with range comparisons to check for read conflicts:
The protocol change would add a
range_end
field to theCompare
protobuf message:The text was updated successfully, but these errors were encountered: