dstepanov-yadro/frostfs-api
1
0
Fork 0
forked from TrueCloudLab/frostfs-api
Code Pull requests Activity

[#136] tombstone: Specify connection with object attribute

Browse source 
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:
Alex Vanin 2021-02-19 12:06:01 +03:00 committed by Alex Vanin
parent a39e0be2bd
commit 1f89c9a0d8
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
tombstone/types.proto
View file

@ -11,7 +11,9 @@ import "refs/types.proto";
// purged from the NeoFS network. // purged from the NeoFS network.
message Tombstone { message Tombstone {
// Last NeoFS epoch number of the tombstone lifetime. It's set by 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"]; uint64 expiration_epoch = 1 [json_name = "expirationEpoch"];
// 16 byte UUID used to identify the split object hierarchy parts. Must be // 16 byte UUID used to identify the split object hierarchy parts. Must be