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
Currently the fileprefix is applied client side. If there are many files in a path then this can be very slow.
A small change to AWSS3DirectoryBrowser would allow the filtering to be applied on the server.
E.g.
Task ListFolderAsync(List<Blob> container, string path, ListOptions options, CancellationToken cancellationToken)
{
var request = new ListObjectsV2Request()
{
BucketName = _bucketName,
Prefix = FormatFolderPrefix(path),
Delimiter = "/" //this tells S3 not to go into the folder recursively
};
// if we have provided a file prefix, then append it on.
// as S3 can perform the filtering at source
if (!string.IsNullOrEmpty(options.FilePrefix))
{
request.Prefix += options.FilePrefix;
}
The text was updated successfully, but these errors were encountered:
Currently the fileprefix is applied client side. If there are many files in a path then this can be very slow.
A small change to AWSS3DirectoryBrowser would allow the filtering to be applied on the server.
E.g.
The text was updated successfully, but these errors were encountered: