You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note, that container has soft-delete option enabled. If this is the reason, then is there any way to get only those blobs that are not marked as deleted?
How can we reproduce the problem in the simplest way?
Create a container, create blobs in the container. Delete some blobs. Call that function. Should see all the blobs.
Have you found a mitigation/solution?
No.
The text was updated successfully, but these errors were encountered:
myfoxtail
changed the title
Deleted blobs are returned in ListBlobsFlatSegment even if Deleted parameter is false
Deleted blobs are returned in ListBlobsFlatSegment if the Version is been requested as well
May 19, 2021
myfoxtail
changed the title
Deleted blobs are returned in ListBlobsFlatSegment if the Version is been requested as well
Deleted blobs are returned in ListBlobsFlatSegment if the Versions is been requested as well
May 19, 2021
Hi @myfoxtail ! Setting Deleted: false should prevent blobs that are soft-deleted from showing up in the list. I tried to repro it and it works as intended. Could you try it out again and maybe provide what steps you are doing before listing the blobs?
Which version of the SDK was used?
v0.13.0
https://pkg.go.dev/github.com/Azure/[email protected]/azblob
Which platform are you using? (ex: Windows, Linux, Debian)
Linux, Mac
What problem was encountered?
Using
ListBlobsFlatSegment
function with the following parameters returns blobs that have been deleted.Note, that container has soft-delete option enabled. If this is the reason, then is there any way to get only those blobs that are not marked as deleted?
How can we reproduce the problem in the simplest way?
Create a container, create blobs in the container. Delete some blobs. Call that function. Should see all the blobs.
Have you found a mitigation/solution?
No.
The text was updated successfully, but these errors were encountered: