Which service(blob, file) does this issue concern?
File Shares
Which version of the SDK was used?
2.0.4
On which platform were you using? (.Net Framework version or .Net Core version, and OS version)
.NET Framework 4.8
How can the problem be reproduced? It'd be better if the code caused the problem can be shared.
Calling UploadAsync(Stream, CloudBlob, UploadOptions, SingleTransferContext, CancellationToken) with a Stream that does not have a Length (i.e. the Length property throws a NotImplementedException.)
What problem was encountered?
I am currently trying to upload a stream with an unknown length to Azure File Shares. These streams are large enough that they cannot be saved to disk. I am using TransferManager.UploadAsync(...) to do the upload. However, since my stream is without length it throws a NotImplementedExceptionwhen being called from UploadAsync. It seems that this question has a known solution when uploading to Blobs, but not to File Shares.
Have you found a mitigation/solution?
If the Length property of a stream throws an exception, then can we allocate some arbitrarily sized chunks on the File Share and start uploading to those chunks? Once UploadAsync reaches the end of the stream, it would concatenate all of the chunks.
Which service(blob, file) does this issue concern?
File Shares
Which version of the SDK was used?
2.0.4
On which platform were you using? (.Net Framework version or .Net Core version, and OS version)
.NET Framework 4.8
How can the problem be reproduced? It'd be better if the code caused the problem can be shared.
Calling UploadAsync(Stream, CloudBlob, UploadOptions, SingleTransferContext, CancellationToken) with a Stream that does not have a Length (i.e. the Length property throws a NotImplementedException.)
What problem was encountered?
I am currently trying to upload a stream with an unknown length to Azure File Shares. These streams are large enough that they cannot be saved to disk. I am using
TransferManager.UploadAsync(...)to do the upload. However, since my stream is without length it throws aNotImplementedExceptionwhen being called fromUploadAsync. It seems that this question has a known solution when uploading to Blobs, but not to File Shares.Have you found a mitigation/solution?
If the Length property of a stream throws an exception, then can we allocate some arbitrarily sized chunks on the File Share and start uploading to those chunks? Once UploadAsync reaches the end of the stream, it would concatenate all of the chunks.