forked from TrueCloudLab/frostfs-api
1f89c9a0d8
Expiration epoch value should be the same in tombstone object body and in tombstone object header. Signed-off-by: Alex Vanin <alexey@nspcc.ru>
26 lines
1 KiB
Protocol Buffer
26 lines
1 KiB
Protocol Buffer
syntax = "proto3";
|
|
|
|
package neo.fs.v2.tombstone;
|
|
|
|
option go_package = "github.com/nspcc-dev/neofs-api-go/v2/tombstone/grpc;tombstone";
|
|
option csharp_namespace = "NeoFS.API.v2.Tombstone";
|
|
|
|
import "refs/types.proto";
|
|
|
|
// Tombstone keeps record of deleted objects for few epochs until they are
|
|
// 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. 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
|
|
// unique inside container. All objects participating in the split must
|
|
// have the same `split_id` value.
|
|
bytes split_id = 2 [json_name = "splitID"];
|
|
|
|
// List of objects to be deleted.
|
|
repeated neo.fs.v2.refs.ObjectID members = 3 [json_name = "members"];
|
|
}
|