Merge lock info into a single attribute #517

New issue

Closed

opened 2025-12-28 17:37:40 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:37:40 +00:00

Owner

Originally created by @roman-khimov on GitHub (May 6, 2025).

Originally assigned to: @smallhive on GitHub.

I'm always frustrated when we're using more attributes than we could. We have S3-BucketSettings-RetentionUntil and S3-BucketSettings-ComplianceMode. Effectively it's all lock metadata, there never a case when we need one of them, but don't need the other, they're never used for searches.

Describe the solution you'd like

Have a single S3-Lock-Meta with JSONised values inside (use more compact time representation like timestamp). This allows to retrieve this attribute alone when searching for objects and get all the lock data for free as well (no need to HEAD the object or perform additional searches).

Originally created by @roman-khimov on GitHub (May 6, 2025). Originally assigned to: @smallhive on GitHub. ## Is your feature request related to a problem? Please describe. I'm always frustrated when we're using more attributes than we could. We have `S3-BucketSettings-RetentionUntil` and `S3-BucketSettings-ComplianceMode`. Effectively it's all lock metadata, there never a case when we need one of them, but don't need the other, they're never used for searches. ## Describe the solution you'd like Have a single `S3-Lock-Meta` with JSONised values inside (use more compact time representation like timestamp). This allows to retrieve this attribute alone when searching for objects and get all the lock data for free as well (no need to HEAD the object or perform additional searches).