[HDDS-793] Support custom key/value annotations on volume/bucket/key

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: Ozone Manager
• Labels: pull-request-available
• Target Version/s: 0.4.0
• Assignee: Marton Elek Assign to me
• Reporter: Marton Elek
• Created: 02/Nov/18 10:22
• Updated: 01/Mar/19 19:14
• Resolved: 25/Jan/19 07:26

Description

I propose to add a custom Map<String,String> annotation field to objects/buckets and keys in Ozone Manager.

It would enable to build any extended functionality on top of the OM's generic interface. For example:

• Support tags in Ozone S3 gateway (https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectGETtagging.html)
• Support md5 based ETags in s3g
• Store s3 related authorization data (ACLs, policies) together with the parent objects

As an optional feature (could be implemented later) the client can defined the exposed annotations. For example s3g can defined which annotations should be read from rocksdb on OM side and sent the the client (s3g)

Issue Links

• blocks: HDDS-792 Use md5 hash as ETag for Ozone S3 objects
• is blocked by: HDDS-748 Use strongly typed metadata Table implementation
• links to: GitHub Pull Request #465