/ azure-sdk-for-net Public
[QUERY] Torn write when using BlobClient's UploadAsync #15863
This issue points to a problem in the data-plane of the library.
Issues that are reported by GitHub users external to the Azure organization.
This issue needs attention from Azure service team or SDK team
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
This issue is responsible by Azure service team.
Storage Service (Queues, Blobs, Files)
Is it possible to run into a situation where a piece of code writes using
UploadAsync, while a consumer using the
DownloadAsyncwould end up with garbled text?
An example: say a writer uploads 20 MB to a block blob, and a reader starts downloading the blob before the writer completes. Will the result of the read be part of those 20 MB, or would the reader be blocked until the upload completes?
The text was updated successfully, but these errors were encountered: