Which service(blob, file, queue, table) does this issue concern?
blob
Which version of the SDK was used?
10.3
What's the Node.js/Browser version?
8.11.1
What problem was encountered?
I have a backing database table that stores additional searchable metadata about each file that gets uploaded into azure storage, such as description, name and other details. There will also be a pseudo directory structure which is all very normal stuff for document management.
I am making a call to uploadBrowserDataToBlockBlob but I cannot see anything in the response that will help me later retrieve the file later.
My code looks like this:
response = await Azure.uploadBrowserDataToBlockBlob(Azure.Aborter.none, file, blockBlobURL, options);
but I can't see anything in that response that will let me later uniquely get this file, unless the blob name is the only thing that I have.
In which case am I best to generate some unique name for the identifier?
Steps to reproduce the issue?
Have you found a mitigation/solution?
Which service(blob, file, queue, table) does this issue concern?
blob
Which version of the SDK was used?
10.3
What's the Node.js/Browser version?
8.11.1
What problem was encountered?
I have a backing database table that stores additional searchable metadata about each file that gets uploaded into azure storage, such as description, name and other details. There will also be a pseudo directory structure which is all very normal stuff for document management.
I am making a call to
uploadBrowserDataToBlockBlobbut I cannot see anything in the response that will help me later retrieve the file later.My code looks like this:
response = await Azure.uploadBrowserDataToBlockBlob(Azure.Aborter.none, file, blockBlobURL, options);but I can't see anything in that response that will let me later uniquely get this file, unless the blob name is the only thing that I have.
In which case am I best to generate some unique name for the identifier?
Steps to reproduce the issue?
Have you found a mitigation/solution?