rich7420 opened a new pull request, #12018:
URL: https://github.com/apache/ozone/pull/12018

   ## What changes were proposed in this pull request?
   
   S3 Gateway's DeleteObjectTagging calls `getS3Volume()` first, which costs a 
separate `GetS3VolumeContext` round trip to OM before the actual request. Like 
DeleteKey in HDDS-16701, it now passes a null volume through the S3 client 
delegation, so OM resolves the S3 volume as part of the DeleteObjectTagging 
request. If an expected-owner check has already loaded the bucket, its volume 
is reused. Clients connected to an OM without `S3_VOLUME_CONTEXT_RESOLUTION` 
still resolve the volume on the client side.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-16703
   
   ## How was this patch tested?
   
   Added DeleteObjectTagging cases to `TestObjectTaggingDelete`, 
`TestS3DeleteObjectTaggingRequest`, `TestRpcClient`, `TestS3ClientProtocol`, 
`TestOzoneManagerProtocolClientSideTranslatorPB` and `TestMultiTenantVolume`; 
each class has a case that fails without the change. `TestMultiTenantVolume` 
covers default, tenant and linked buckets; its S3 client setup moved into 
`newS3Client(ObjectStore)` so the delete-key and delete-tagging checks share it.
   
   CI (pending): https://github.com/rich7420/ozone/actions/runs/42992146765
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to