-
Notifications
You must be signed in to change notification settings - Fork 653
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
Feat s3 transfer manager v2 PutObject #2733
Conversation
Tests are failing. I know that some of the business logic is duplicated from the original version here, but I'm reviewing it as if it's all new. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to seriously re-examine the part pool behavior. It seems entirely overcomplicated for what we need out of it.
We need to discuss how we manage maximum part size of 10k for MPUs - failing on an in-progress download from exceeding the limit after the fact isn't acceptable behavior.
f3a43fb
to
ba7b247
Compare
e4c3fe7
to
734b574
Compare
merge main dev branch into current feature branch
ExpectError string | ||
} | ||
|
||
func testPutObject(t *testing.T, bucket string, testData putObjectTestData, opts ...func(options *tm.Options)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice
Implement v2 s3 transfer manager's putobject api bound to single union client which mimics normal service client's initialization and api call.
Test: passed unit test for putobject and pool, passed integration test of uploading object via transfer manager v2 and validating its content after downloading through s3 client