forked from TrueCloudLab/frostfs-api
[#221] lock: Clarify lock object usage
Signed-off-by: Pavel Karpy <carpawell@nspcc.ru>
This commit is contained in:
parent
64ab86a1ff
commit
e31fcad6b8
1 changed files with 2 additions and 1 deletions
|
@ -9,7 +9,8 @@ import "refs/types.proto";
|
||||||
|
|
||||||
// Lock objects protects a list of objects from being deleted. The lifetime of a
|
// Lock objects protects a list of objects from being deleted. The lifetime of a
|
||||||
// lock object is limited similar to regular objects in
|
// lock object is limited similar to regular objects in
|
||||||
// `__NEOFS__EXPIRATION_EPOCH` attribute.
|
// `__NEOFS__EXPIRATION_EPOCH` attribute. Lock object MUST have expiration epoch.
|
||||||
|
// It is impossible to delete a lock object via ObjectService.Delete RPC call.
|
||||||
message Lock {
|
message Lock {
|
||||||
// List of objects to lock. Must not be empty or carry empty IDs.
|
// List of objects to lock. Must not be empty or carry empty IDs.
|
||||||
// All members must be of the `REGULAR` type.
|
// All members must be of the `REGULAR` type.
|
||||||
|
|
Loading…
Reference in a new issue