Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[QUERY] BlockBlobClient.OpenWriteAsync with overwrite: false
See original GitHub issueQuery/Question
If I call BlockBlobClient.OpenWriteAsync(overwrite: false) I get 'System.ArgumentException' in System.Private.CoreLib.dll: 'BlockBlobClient.OpenWrite only supports overwriting'. Why can’t I set overwrite to false? If I set overwrite: true and then set options: new BlockBlobOpenWriteOptions { OpenConditions = new BlobRequestConditions { IfNoneMatch = new ETag("*") } } it seems to behave as it should, throwing an exception if I try to open a blob that already exists.
Environment:
- Name and version of the Library package used: Azure.Storage.Blobs 12.10.0
- Hosting platform or OS and .NET runtime version (
dotnet --infooutput for .NET Core projects): Windows 10 .NET 5
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ok, thanks. I thought of that, but then dismissed it because it seemed so inconsistent with the rest of the use of the word “overwrite” in the API, and because the API docs did not say that it is what it meant. When re-reading it after your message, I can see the docs could mean both things “Whether an existing blob should be deleted and recreated.”
Note: this workaround is not fool proof for Archived blobs – if you’re catching a
409 BlobAlreadyExists, in case of an archived blob it throws a409 BlobArchived