forked from TrueCloudLab/frostfs-api
[#136] tombstone: Specify connection with object attribute
Expiration epoch value should be the same in tombstone object body and in tombstone object header. Signed-off-by: Alex Vanin <alexey@nspcc.ru>
This commit is contained in:
parent
a39e0be2bd
commit
1f89c9a0d8
1 changed files with 3 additions and 1 deletions
|
@ -11,7 +11,9 @@ import "refs/types.proto";
|
|||
// purged from the NeoFS network.
|
||||
message Tombstone {
|
||||
// Last NeoFS epoch number of the tombstone lifetime. It's set by tombstone
|
||||
// creator depending on current NeoFS network settings.
|
||||
// creator depending on current NeoFS network settings. Tombstone object
|
||||
// must have the same expiration epoch value in `__NEOFS__EXPIRATION_EPOCH`
|
||||
// attribute. Otherwise tombstone will be rejected by storage node.
|
||||
uint64 expiration_epoch = 1 [json_name = "expirationEpoch"];
|
||||
|
||||
// 16 byte UUID used to identify the split object hierarchy parts. Must be
|
||||
|
|
Loading…
Reference in a new issue