From e31fcad6b85f0d7f4565e9adc4a5d204b9f7872a Mon Sep 17 00:00:00 2001 From: Pavel Karpy Date: Fri, 27 May 2022 14:54:48 +0300 Subject: [PATCH] [#221] lock: Clarify lock object usage Signed-off-by: Pavel Karpy --- lock/types.proto | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lock/types.proto b/lock/types.proto index edf141e..da811b8 100644 --- a/lock/types.proto +++ b/lock/types.proto @@ -9,7 +9,8 @@ import "refs/types.proto"; // Lock objects protects a list of objects from being deleted. The lifetime of a // 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 { // List of objects to lock. Must not be empty or carry empty IDs. // All members must be of the `REGULAR` type.