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
I have a bucket with versioning enabled, that contains these objects, as seen in the MinIO web UI:
Note that I have the Show deleted objects option selected, and the object named links.csv has been deleted. Also this is the full version history of links.csv:
I'm using version 5.0.0 of the Nuget package, and calling ListObjectsAsync(listArgs) with a parameter like
new ListObjectsArgs()
.WithBucket("document-management-test")
.WithPrefix("DirA/")
.WithRecursive(false)
.WithVersions(true);
The results include records for both objects, and specifically there are two records for links.csv representing the first two versions (dff166a9 and f3d45bdc), but none representing the fact that the object was deleted.
Should the 'deleted' version be appearing in these results or is there some other intended way to know the object is in a deleted state?
The text was updated successfully, but these errors were encountered:
brettzook
changed the title
How to detect deleted files with call to ListObjectsAsync()
How to detect deleted objects with call to ListObjectsAsync()
Jul 25, 2023
I have a bucket with versioning enabled, that contains these objects, as seen in the MinIO web UI:
Note that I have the Show deleted objects option selected, and the object named
links.csv
has been deleted. Also this is the full version history oflinks.csv
:I'm using version 5.0.0 of the Nuget package, and calling
ListObjectsAsync(listArgs)
with a parameter likeThe results include records for both objects, and specifically there are two records for
links.csv
representing the first two versions (dff166a9
andf3d45bdc
), but none representing the fact that the object was deleted.Should the 'deleted' version be appearing in these results or is there some other intended way to know the object is in a deleted state?
The text was updated successfully, but these errors were encountered: