azure-storage-js | Microsoft Azure Storage Library for JavaScript ( This repo | Azure library
kandi X-RAY | azure-storage-js Summary
kandi X-RAY | azure-storage-js Summary
This project has been moved to the azure-sdk-for-js repository, specifically under This repository is no longer maintained. For new issues and pull requests, please go to azure-sdk-for-js repository.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of azure-storage-js
azure-storage-js Key Features
azure-storage-js Examples and Code Snippets
Community Discussions
Trending Discussions on azure-storage-js
QUESTION
I'm following the example here https://github.com/Azure/azure-storage-js/blob/master/blob/samples/basic.sample.js about reading a Blob from Azure Blob Storage to a string using the Node.js SDK.
The blob I'm trying to read is an Append Blob.
First of all reading the stream into a string takes a really long time and in the end I get a HTTP 412 error.
I also asked this question here: https://github.com/Azure/azure-storage-js/issues/51
I'm doing this with Node.js v10.14.1 and the SDK I'm using is @azure/storage-blob@10.3.0.
My code is here:
...ANSWER
Answered 2019-Jan-11 at 02:04This questions has been resolved in GitHub issue https://github.com/Azure/azure-storage-js/issues/51 Copy solution from GitHub issue to here.
blobURL.download() will try to download a blob with a HTTP Get request into a stream. When stream unexpected ends due to such as network broken, a retry will resume the stream read from the broken point with a new HTTP Get request.
The second HTTP request will use conditional header IfMatch with the blob's ETag returned in first request to make sure the blob doesn't change when the 2nd retry happens. Otherwise, a 412 conditional header doesn't match error will be returned. This strict strategy is used to avoid data integrity issues, such as the blob maybe totally over written by someone others. However, this strategy seems avoiding you from reading a constantly updated log file when a retry happens.
While I don't think it's bug, but we need to make this scenario work for you. Please have a try with following solution: snapshot the append blob first, and read from the snapshot blob
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install azure-storage-js
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page