You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.
However when the mock is used it fails with AmazonS3Exception: Not Found (Service: Amazon S3; Status Code: 404; Error Code: 404 Not Found; Request ID: null), S3 Extended Request ID: null error.
When used with S3 service the client behaves as expected.
The text was updated successfully, but these errors were encountered:
This also happens for multi-object delete requests. It throws a MultiObjectDeleteException
with the code null and message One or more objects could not be deleted (Service: null; Status Code: 200; Error Code: null; Request ID: null; S3 Extended Request ID: null).
The DeleteError objects contained by the exception are all like this: code=InternalError, message=Cannot delete.
Expected would be to return a successful result where the missing keys are still included as deleted objects, at least this is the current S3 behaviour.
According to documentation for Java SDK client,
deleteObject
succeeds when object with a given key does not exist.However when the mock is used it fails with
AmazonS3Exception: Not Found (Service: Amazon S3; Status Code: 404; Error Code: 404 Not Found; Request ID: null), S3 Extended Request ID: null
error.When used with S3 service the client behaves as expected.
The text was updated successfully, but these errors were encountered: