[ 
https://issues.apache.org/jira/browse/HDDS-15512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDDS-15512:
----------------------------------
    Labels: pull-request-available  (was: )

> Implement S3 PUT/GET/DELETE ?tagging on buckets with validation, metrics, and 
> smoketest
> ---------------------------------------------------------------------------------------
>
>                 Key: HDDS-15512
>                 URL: https://issues.apache.org/jira/browse/HDDS-15512
>             Project: Apache Ozone
>          Issue Type: Sub-task
>    Affects Versions: 2.2.0
>            Reporter: Gargi Jaiswal
>            Assignee: Gargi Jaiswal
>            Priority: Major
>              Labels: pull-request-available
>
> Expose AWS S3-compatible bucket tagging over HTTP at 
> {color:#00875a}{{/{bucket}?tagging}}{color}. Validate XML input per AWS rules 
> (max 50 tags, key/value length limits, no duplicate keys, no {{aws:}} 
> prefix). Map OM {color:#de350b}{{NoSuchTagSet}}{color} behavior on GET when 
> no tags exist.
> Scope:
>  * {{*BucketTaggingHandler.java*}} — PUT/GET/DELETE handlers
>  * *{{BucketEndpoint.java}}* — route {{?tagging}} sub-resource
>  * *{{EndpointBase.validateAndGetTagging()}}* — reuse with 
> {{S3Consts.TAG_BUCKET_NUM_LIMIT}} (50)
>  * *{{S3Tagging.java}}* — XML model (if not shared with object tagging)
>  * {{*S3GatewayMetrics.java*}} ** — success/failure counters and latency
>  * {{*S3GAction*}} audit entries
>  * Unit tests
>  ** {{*TestBucketTaggingPut.java*}} — validation, malformed XML, limits
>  ** {{*TestBucketTaggingGet.java*}} ** — happy path, {{NoSuchTagSet}}
>  ** {{*TestBucketTaggingDelete.java*}}
>  ** *{{TestS3GatewayMetrics.java}}* — metric updates
>  * Acceptance test
>  ** *{{buckettagging.robot}} —* full put/get/delete/overwrite flow via {{aws 
> s3api}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to