Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

Error when deleting non-existing key #97

Open
sgraca opened this issue Mar 16, 2018 · 3 comments
Open

Error when deleting non-existing key #97

sgraca opened this issue Mar 16, 2018 · 3 comments

Comments

@sgraca
Copy link

sgraca commented Mar 16, 2018

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.

@rtvlad
Copy link

rtvlad commented Apr 12, 2018

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.

@manuelcueto
Copy link

Hey guys, just submitted a pull request ( #109 ) addressing this issue.
cheers!, Manuel.

@rtvlad
Copy link

rtvlad commented Feb 20, 2019

Hi! Added a comment on that PR, hopefully it can be merged soon.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants