feat: s3 transfer manager v2 #3079
Conversation
This is an initial phase for the s3 transfer manager v2, which includes: - Progress Tracker with a default Console Progres Bar. - Dedicated Multipart Download Listener for listen to events specificly to multipart download. - Generic Transfer Listener that will be used in either a multipart upload or a multipart download. The progress tracker is dependant on the Generic Transfer Listener, and when enabled it uses the same parameter to be provided as the progress tracker. This is important because if there is a need for listening to transfer specific events and also track the progress then, a custom implementation must be done that incorporate those two needs together, otherwise one of each other must be used. - Single Object Download - Multipart Objet Download This initial implementation misses the test cases.
- Refactor set a single argument, even when not exists, in the console progress bar. - Add a specific parameter for showing the progress rendering defaulted to STDOUT. - Add test cases for ConsoleProgressBar. - Add test cases for DefaultProgressTracker. - Add test cases for ObjectProgressTracker. - Add test cases for TransferListener.
- Add test cases for multipart download listener.
- Add a trait to the MultipartDownloader implementation to keep the main implementatio cleaner. - Add test cases for multipart downloader, in specific testing part and range get multipart downloader.
Refactor: - Moves opening braces into a new line. - Make requestArgs an optional argument. - Remove unnecessary traits. - Use traditional declarations. Adds: - Download directory feature.
Refactor: - Add a message placeholder for progress status. For example in case of errors. Adds: - Upload feature, missing multipart functionality.
- Add upload directory feature
- Add a dedicated multipart upload implementation - Add transfer progress to multipart upload - Add upload directory with the required options. - Create specific response models for upload, and upload directory. - Add multipart upload test cases. - Fix transfer listener completation eval.
Short namespace from `Aws\S3\Features\S3Transfer` to `Aws\S3\S3Transfer`.
There was a problem hiding this comment.
A few more comments- I think a few from the last round were left addressed also. I'd do another check for function opening braces (needing to be moved to a new line) and new files that are missing a newline at the end. More test classes needed as well but I'm assuming those are on the way
- Implement progress tracker based on SEP spec. - Add a default progress bar implementation. - Add different progress tracker formats: -- Plain progress format: [|progress_bar|] |percent|% -- Transfer progress format: [|progress_bar|] |percent|% |transferred|/|tobe_transferred| |unit| -- Colored progress format: |object_name|:\n\033|color_code|[|progress_bar|] |percent|% |transferred|/|tobe_transferred| |unit| |message|\033[0m - Add a default single progress tracker implementation. - Add a default multi progress tracker implementation for tracking directory transfers. - Include tests unit just for console progress bar.
- Fixes current test cases for: - MultipartUploader - MultipartDownloader - ProgressTracker
- Remove progress bar color enum since the colors were moved into the specific format that requires them.
TransferListener must be tested from the implementations that extends and use this abstract class.
Add nullable type to listenerNotifier property in the MultipartUploader implementation.
- Tests for MultiProgressTracker - Tests for SingleProgressTracker - Tests for ProgressBarFormat - Tests for TransferProgressSnapshot - Tests for TransferListenerNotifier
- Refactor code to address some styling related feedback. - Add upload and uploadDirectory unit tests.
- Fix MultipartUpload tests by increasing the part size from 1024 to 10240000 so it gets between the allowed part size range 5MB-5GBs. - Rename tobe to to_be in the progress formatting.
- Add download tests - Add download directory tests - Minor naming refactor
src/S3/S3Transfer/Progress/ColoredTransferProgressBarFormat.php
Outdated
Show resolved
Hide resolved
src/S3/S3Transfer/Progress/ColoredTransferProgressBarFormat.php
Outdated
Show resolved
Hide resolved
- Add upload integ tests for: - Single uploads - Multipart uploads - Checksum in single uploads - Checksum in multipart uploads - Add download integ tests for: - Single downloads - Multipart downloads
- Add integ tests for directory uploads - Add integ tests for directory downloads
There was a problem hiding this comment.
Mostly nits, but the most important requests are: adding upload() and download() methods on the uploader and downloader classes that call promise() (similar to the old implementation)and testing the resolvesOutsideTargetDirectory logic.
I would do an audit of hard-coded values that can be moved to classes, line length (max 85 char) and all new files that do not end with a newline.
- Move some fixed values out of the methods into consts. - Address a line exceeded 80 chars. - Declare keys used across different implementations as consts.
- Fix keys declaration in TransferListener.php - Make use of DIRECTORY_SEPARATOR const instead of hardcoding `/`
- Some implementations using TransferListener were missing the import statement.
- Make config arguments optional - Make getObjectRequest/putObjectRequest argument optional - Delete file if exists when using the file download handler.
- Make getObjectRequestArgs optional in download directory operation. - Add config key in docs
|
|
||
| namespace Aws\S3\S3Transfer\Models; | ||
|
|
||
| class DownloadDirectoryResponse |
There was a problem hiding this comment.
can we change this to DownloadDirectoryResult and extend Aws\Result?
There was a problem hiding this comment.
I am not sure what would be the use case right now for doing this. This class just holds how many uploads failed and how many succeeded. So it is not hold any other data.
There was a problem hiding this comment.
Got it. I think the name change should still apply. Is there a way to expose (a group of) the individual DownloadResult objects here?
There was a problem hiding this comment.
Yes, I think we should expose the download results here. Or at least for failed request. I will think what could be the best approach here, because, I don't want to have a class holding so many results which could cause unnecessary memory consumption.
There was a problem hiding this comment.
Agreed. Probably not ideal for successful downloads. But we should probably include all of the results for successful uploads on its corresponding class
| * | ||
| * @return PromiseInterface | ||
| */ | ||
| public function download( |
There was a problem hiding this comment.
Probably the wrong entry point for the comment, but I saw we had recursive directory upload functionality. We should have that for downloads as well per the spec, but I don't think that's a hard requirement
- Make data model final - Refactor test cases to use correct parameters for S3TransferManager APIs
- Fix S3TransferManagetContext.php to use the correct parameter expected in the different APIs exposed by S3TranserManager - Refactor some formatting styling.
- Added empty line at the end of files. - Add a more descriptive documentation in $failsWhenDestinationExists. - Remove unnecessary break line.
- Remove spaces between union type definitions - Add documentation for config parameters in UploadDirectoryRequest. - Add missing new lines in a few places.
- Rename upload and download request args. - Refactor tests to clean up resources specifically in the finally block instead of using cleanUpFns. - Add Throwable and Result type. - Make parameter optional by adding a default value.
- Source should have been provided as null when the bucket and key are already provided as part of the download request args. - When checksum type will be resolved to FULL_OBJECT the only supported algorithms are CRC family.
yenfryherrerafeliz
force-pushed
the
feat_s3_transfer_manager_v2
branch
from
847cda0 to
e7842ed
Compare
- Fix checksum parameter in the request should have been ChecksumCRC32 and no ChecksumCrc32. - Validates next part fetched in a multipart download operation is sequentially correct. - Fix checksum calculation in multipart parts processing. It should have been base64 encoded and the hash_final should have been the binary. - Prevents parts uploading when there was a failure and its running with concurrency. For example, when running in concurrency parts may not be uploaded in order and a failure in one part was not preventing other parts from being uploaded. This fix prevents any part from being uploaded after a failure happened. - Forces multipart_download_type parameter to be lowercase, even when provided as upper case. - Add tests to validate input fields are copied in the different multipart upload operations. - Add tests to validate IfMatch is present in subsequent part or range get requests. - Add test runners for upload and download for modeled test cases.
- Expected part count validation was added and hence in the tests where not part counts were provided a failure was happening. - Replace rmdir by the clean up directory helper method from the TestUtility implementation.
- Rename Exceptions to Exception
| $filter = $config['filter']; | ||
| } | ||
|
|
||
| $putObjectRequestCallback = null; |
There was a problem hiding this comment.
Apologies if I missed this before, but I think this is sort of the same as the putObjectRequestArgs -> uploadRequestArgs comments I've made previously. The name implies that it will only be used for putObject operations. Maybe objectUploadRequestCalback?
There was a problem hiding this comment.
This is how it was defined by the specifications.
- Remove full object checksum calculate since it is not recommended. - Address some styling issues.
- Make some statements multilines. - Add comments describing functionality.
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.