Gargi-jais11 opened a new pull request, #9340:
URL: https://github.com/apache/ozone/pull/9340

   ## What changes were proposed in this pull request?
   On **AWS S3, AbortMultipartUpload** with the same upload id will always get 
**204 No Content**.
   But on **MinIO,** when the client repeats the same AbortMultipartUpload 
request, as the resource has already been deleted, the server returns 404 Not 
Found.
   The behaviour should be consistent with AWS S3.
   If AbortMultipartUpload request is given a non-existent key, it should 
respond 204 No Content (no exception) instead of 404.
   
   Related discussion for this :
   https://github.com/minio/minio/discussions/13495
   ## What is the link to the Apache JIRA
   https://issues.apache.org/jira/browse/HDDS-13740
   
   ## How was this patch tested?
   Updated unit test : `TestAbortMultipartUpload` and `TestS3GatewayMetrics`
   Updated acceptance test: `MultipartUpload.robot`
   


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