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

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

> Reuse bucket metadata after owner verification in S3 
> PutBucketLifecycleConfiguration
> ------------------------------------------------------------------------------------
>
>                 Key: HDDS-16649
>                 URL: https://issues.apache.org/jira/browse/HDDS-16649
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Huang Kuan Hao
>            Assignee: Huang Kuan Hao
>            Priority: Major
>              Labels: pull-request-available
>
> When a request includes a non-empty x-amz-expected-bucket-owner header, 
> BucketLifecycleHandler retrieves the bucket to verify its owner. After 
> verification succeeds, putBucketLifecycleConfiguration retrieves the same 
> bucket again to construct and set the
>  lifecycle configuration.  Reuse the OzoneBucket obtained during owner 
> verification. Retain the existing lookup when the header is absent or empty. 
> This saves one bucket metadata lookup for requests that pass expected-owner 
> verification, while preserving the existing bucket READ requirement, owner 
> validation, bucket layout handling, and OM authorization.
>   Regression tests should verify:
>   * One bucket metadata lookup with absent, empty, or matching expected-owner 
> headers.
>   * Owner mismatch and lookup failures still prevent the update, with the 
> existing error mapping and validation order.
>   * Malformed XML handling and propagation of OBS/FSO bucket layout remain 
> unchanged.



--
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