[jira] [Assigned] (HDDS-16702) S3G: Avoid calling getS3Volume in MULTI_DELETE

["dino2895 (Jira)" <ji...@apache.org>]

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

dino2895 reassigned HDDS-16702:
-------------------------------

    Assignee: dino2895

> S3G: Avoid calling getS3Volume in MULTI_DELETE
> ----------------------------------------------
>
>                 Key: HDDS-16702
>                 URL: https://issues.apache.org/jira/browse/HDDS-16702
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Chung-En Lee
>            Assignee: dino2895
>            Priority: Major
>
> Background & Problem
> In `MultiDeleteEndpoint`, S3G receives a batch delete request and invokes `getS3VolumeContext` before executing deletions. While batch delete handles multiple keys at once, the initial volume resolution step is still redundant and can be handled directly by OM.
> Proposed Solution
> 1. Allow OM's batch deletion handler (`deleteKeys` / `OmDeleteKeysRequest`) to accept S3 bucket context natively via `assumeS3Context=true`.
> 2. Refactor `MultiDeleteEndpoint` to eliminate the preliminary `getS3VolumeContext` call.
> Expected Impact
> Eliminates the initial lookup RTT before batch delete processing starts.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org