service/s3/s3manager: Document default behavior for Upload's MaxNumParts #2077
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updates the S3 Upload Manager's default behavior for MaxNumParts, and ensurs that the Uploader.MaxNumPart's member value is initialized properly if the type was created via struct initialization instead of using the `NewUploader` function. Fix aws#2015
xibz
approved these changes
Jul 26, 2018
Merged
diehlaws
added
needs-review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the S3 Upload Manager's default behavior for MaxNumParts, and
ensures that the Uploader.MaxNumPart's member value is initialized
properly if the type was created via struct initialization instead of
using the
NewUploaderfunction.Fix #2015