Please check if the PR fulfills these requirements
[x] The commit message describes your change
[x] Tests for the changes have been added if possible (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[ ] Changes are mentioned in the changelog (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feature
What is the current behavior? (You can also link to an open issue here)
All download are running in parallel. By parallel we mean the parts composing a file is downloaded in parallel.
What is the new behavior (if this is a feature change)?
If user enable the option, the download are not running in parallel
Behavior doesn't change if the user don't enable the option.
Does this PR introduce a breaking change? (What changes might users need to make in their setup due to this PR?)
No, it is just feature flag
Some provider fails to comply with s3 parallel downloads. Add an option to disable it
http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/transfer/TransferManager.html#download(com.amazonaws.services.s3.model.GetObjectRequest,%20java.io.File,%20com.amazonaws.services.s3.transfer.internal.S3ProgressListener) AWS announce of parallel download: https://aws.amazon.com/blogs/developer/parallelizing-large-downloads-for-optimal-speed/
Please check if the PR fulfills these requirements
[x] The commit message describes your change
[x] Tests for the changes have been added if possible (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[ ] Changes are mentioned in the changelog (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) feature
What is the current behavior? (You can also link to an open issue here) All download are running in parallel. By parallel we mean the parts composing a file is downloaded in parallel.
What is the new behavior (if this is a feature change)? If user enable the option, the download are not running in parallel Behavior doesn't change if the user don't enable the option.
Does this PR introduce a breaking change? (What changes might users need to make in their setup due to this PR?) No, it is just feature flag