Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[chore] fix typo #273

Merged
merged 1 commit into from
Nov 6, 2023
Merged

[chore] fix typo #273

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -333,7 +333,7 @@ deleted between these two operations. Therefore, we currently always return `tru

Our implementation of `FileSystemProvider.copy` will also copy the content of the directory via batched copy operations. This is a variance
from some other implementations such as `UnixFileSystemProvider` where directory contents are not copied and the
use of the {@code walkFileTree} is suggested to perform deep copies. In S3 this could result in an explosion
use of the `walkFileTree` method is suggested to perform deep copies. In S3 this could result in an explosion
of API calls which would be both expensive in time and possibly money. By performing batch copies we can greatly reduce
the number of calls.

Expand Down