[ 
https://issues.apache.org/jira/browse/HDDS-793?focusedWorklogId=184253&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-184253
 ]

ASF GitHub Bot logged work on HDDS-793:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Jan/19 16:05
            Start Date: 11/Jan/19 16:05
    Worklog Time Spent: 10m 
      Work Description: elek commented on pull request #465: HDDS-793. Support 
custom key/value annotations on volume/bucket/key.
URL: https://github.com/apache/hadoop/pull/465
 
 
   See: https://issues.apache.org/jira/browse/HDDS-793
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 184253)
            Time Spent: 10m
    Remaining Estimate: 0h

> 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
>
>          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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to