-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix/Clarify lock object usage #221
Fix/Clarify lock object usage #221
Conversation
lock/types.proto
Outdated
@@ -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 lock object via ObjectService.Delete RPC call. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to delete A lock object
, sorry, missed that before.
Signed-off-by: Pavel Karpy <[email protected]>
Decided not to wait for some tests? |
Well, seems like that. |
See nspcc-dev/neofs-node#1227 (comment) for details.
Think it could wait until the whole implementation is ready and testing to prevent any breaking changes in the future (in fact I think that PR is already a breaking change).