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
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.
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.
Is the container
delete-objects
function intended to offer any guarantees about atomicity? If not, what behaviour is expected on partial failure?The text was updated successfully, but these errors were encountered: