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.

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

Add download implementation for API requests #1231

Merged

Conversation

dagnir
Copy link
Contributor

@dagnir dagnir commented Apr 26, 2019

Description

Basic implementation for download.

Motivation and Context

Testing

New unit and integration tests.

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have read the README document
  • I have added tests to cover my changes
  • All new and existing tests passed
  • A short description of the change has been added to the CHANGELOG
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

  • I confirm that this pull request can be released under the Apache 2 license

* @param <ResponseT> Pojo Response type.
* @return AsyncResponseTransformer instance.
*/
static <ResponseT> AsyncResponseTransformer<ResponseT, ResponseT> toFile(Path path,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note: I have another PR for this in #1222 that will be merged to master. I will update the s3-transfermanager branch once it goes through. Just didn't want it to hold this PR up.

@dagnir dagnir force-pushed the s3-transfermanager-download-obj branch 2 times, most recently from 6cc2e18 to bd8f532 Compare April 26, 2019 16:33
@spfink
Copy link
Contributor

spfink commented Apr 26, 2019

Should we look into doing experimental releases to Maven?

@dagnir
Copy link
Contributor Author

dagnir commented Apr 26, 2019

@spfink Yes, eventually, I'd like to make preview releases available on Maven. I imagine we'll be doing the same for the DDB enhanced client.

cc: @millems

private void validateConfig() {
Validate.isPositive(multipartUploadThreshold, "multipartUploadThreshold");
Validate.isPositive(minUploadPartSize, "minUploadPartSize");
Validate.isTrue(minUploadPartSize <= multipartUploadThreshold,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why minUploadPartSize should be less than multipartUploadThreshold? It makes sense but should not be a requirement. Customer might have large objects like 1 GB and they want part size to be 50 MB or so. In that we should do 50MB parts instead of forcing them to 16MB parts.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. I'll change to 5MiB, since that's the absolute min set by S3.

Copy link
Contributor

@varunnvs92 varunnvs92 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had one comment. Other than that, lgtm.

@dagnir dagnir force-pushed the s3-transfermanager-download-obj branch from 1b951c5 to f94555a Compare May 9, 2019 21:42
@dagnir dagnir merged commit 028fe92 into aws:s3-transfermanager May 9, 2019
aws-sdk-java-automation added a commit that referenced this pull request Mar 17, 2021
…30a0c1726

Pull request: release <- staging/3ae227e0-77a6-4cca-ac60-79a30a0c1726
This was referenced Mar 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants