Store epoch timestamp for all lifecycle expiration targets #412

New issue

Closed

opened 2024-06-27 14:27:45 +00:00 by alexvanin · 1 comment

alexvanin commented

2024-06-27 14:27:45 +00:00

Owner

To perform object deletion or abort multipart upload, lifecycler service must know timestamp when lifecycle target was created. Consider lifecycle targets are:

regular objects,
complete-multipart-uploads.

Make sure that entities store creation timestamp in the tree service.

To perform object deletion or abort multipart upload, lifecycler service must know timestamp when lifecycle target was created. Consider lifecycle targets are: * regular objects, * complete-multipart-uploads. Make sure that entities store creation timestamp in the tree service.

alexvanin added this to the v0.31.0 milestone 2024-06-27 14:27:45 +00:00

alexvanin commented

2024-06-27 14:34:11 +00:00

Author

Owner

~~By the way, it would be cool if node returns current epoch in x-header. It is not necessary, but it looks pretty.~~

Nevermind, it already does.

sequenceDiagram
  S3 ->>+ ObjService: Put Object
  ObjService ->>- S3: ObjectID + Timestamp (X-Header)
  S3 ->> Tree: ObjectInfo

/cc @fyrchik , @dkirillov

~~By the way, it would be cool if node returns current epoch in x-header. It is not necessary, but it looks pretty.~~ Nevermind, it already does. ```mermaid sequenceDiagram S3 ->>+ ObjService: Put Object ObjService ->>- S3: ObjectID + Timestamp (X-Header) S3 ->> Tree: ObjectInfo ``` /cc @fyrchik , @dkirillov