refactor: remove ObjectUplaoder and turn stream uploading
#1227
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
trim21
changed the title
ObjectUplaoder and turn stream uploading
aldy505
reviewed
Nov 24, 2023
getContentLength function
prakashsvmx
approved these changes
Nov 27, 2023
kaankabalak
approved these changes
Nov 27, 2023
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.
ref #1045
previously, if user want to upload a stream, for example:
s3.putObject('...', '...', fs.createReadStream('...')), minio-js will usemaxObjectSizeas object size and 500 mb as chunk size.after this patch, when
putObjectis used with a stream created byfs.createReadStream, minio-js will try to read file size as object size, and use proper chunk size.