Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

container::delete-objects semantics #30

Open
itowlson opened this issue Oct 15, 2024 · 2 comments
Open

container::delete-objects semantics #30

itowlson opened this issue Oct 15, 2024 · 2 comments

Comments

@itowlson
Copy link

Is the container delete-objects function intended to offer any guarantees about atomicity? If not, what behaviour is expected on partial failure?

@Mossaka
Copy link
Collaborator

Mossaka commented Oct 17, 2024

I do not believe delete-objects offers any guarantees about atomicity.

If not, what behaviour is expected on partial failure?

I think we should clarify this in the docs of this operation. In particular, I do believe it would be helpful to return a list of keys that are deleted successfully and an error message indicating that there is a partial failure, similar to the semantics of DeleteObjects in s3.

Interestingly, azure blob store does not support delete-objects operation.

CC @thomastaylor312

@itowlson
Copy link
Author

Interestingly, azure blob store does not support delete-objects operation.

Indeed... I (rather foolishly) picked Azure as my first try to implement wasi-blobstore and ran slap bang into this! There is a "blob batch" API but the SDK for my language doesn't surface it.

container::clear() seems not to exist in Azure either.

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

No branches or pull requests

2 participants