[
https://issues.apache.org/jira/browse/HDDS-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751990#comment-16751990
]
Xiaoyu Yao edited comment on HDDS-793 at 1/25/19 7:27 AM:
----------------------------------------------------------
Thanks [~elek] for the update. Patch v4 LGTM, +1. I've commit the patch v4 to
trunk.
was (Author: xyao):
Thanks [~elek] for the contribution. I've commit the patch v4 to trunk.
> Support custom key/value annotations on volume/bucket/key
> ---------------------------------------------------------
>
> Key: HDDS-793
> URL: https://issues.apache.org/jira/browse/HDDS-793
> Project: Hadoop Distributed Data Store
> Issue Type: New Feature
> Components: OM
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Labels: pull-request-available
> Attachments: HDDS-793.001.patch, HDDS-793.002.patch,
> HDDS-793.003.patch, HDDS-793.004.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
