-
Notifications
You must be signed in to change notification settings - Fork 233
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
native multi-part upload #2
Comments
gaul
added a commit
that referenced
this issue
Jan 3, 2015
This approach requires three times as many operations as the optimal approach. Implementing this correctly requires exposing the underlying multipart operations in jclouds. Most s3-tests pass but two still fail: test_multipart_upload_size_too_small test_list_multipart_upload References #2.
gaul
added a commit
that referenced
this issue
Jan 3, 2015
This approach requires three times as many operations as the optimal approach. Implementing this correctly requires exposing the underlying multipart operations in jclouds. Most s3-tests pass but two still fail: test_multipart_upload_size_too_small test_list_multipart_upload References #2.
gaul
added a commit
that referenced
this issue
Jan 12, 2015
This approach requires three times as many operations as the optimal approach. Implementing this correctly requires exposing the underlying multipart operations in jclouds. Most s3-tests pass but two still fail: test_multipart_upload_size_too_small test_list_multipart_upload References #2.
gaul
added a commit
that referenced
this issue
Jan 14, 2015
This approach requires three times as many operations as the optimal approach. Implementing this correctly requires exposing the underlying multipart operations in jclouds. Most s3-tests pass but two still fail: test_multipart_upload_size_too_small test_list_multipart_upload References #2.
gaul
added a commit
that referenced
this issue
Jan 21, 2015
This approach requires three times as many operations as the optimal approach. Implementing this correctly requires exposing the underlying multipart operations in jclouds. Most s3-tests pass but two still fail: test_multipart_upload_size_too_small test_list_multipart_upload References #2.
gaul
added a commit
that referenced
this issue
Feb 21, 2015
This approach requires three times as many operations as the optimal approach. Implementing this correctly requires exposing the underlying multipart operations in jclouds. Most s3-tests pass but one still fails: test_list_multipart_upload References #2.
gaul
added a commit
that referenced
this issue
Mar 1, 2015
This approach requires three times as many operations as the optimal approach. Implementing this correctly requires exposing the underlying multipart operations in jclouds. Most s3-tests pass but test_list_multipart_upload still fails: References #2.
gaul
added a commit
that referenced
this issue
Mar 1, 2015
This approach requires three times as many operations as the optimal approach. Implementing this correctly requires exposing the underlying multipart operations in jclouds. Most s3-tests pass but test_list_multipart_upload still fails: References #2.
gaul
added a commit
that referenced
this issue
Mar 2, 2015
This approach requires three times as many operations as the optimal approach. Implementing this correctly requires exposing the underlying multipart operations in jclouds. Most s3-tests pass but test_list_multipart_upload still fails: References #2.
gaul
added a commit
that referenced
this issue
Mar 3, 2015
Previously InitiateMultipartUpload used the incorrect length. Found with s3fs integration tests. References #2.
gaul
added a commit
that referenced
this issue
Apr 28, 2015
Fixes #2. Do not commit; requires: jclouds/jclouds#737
gaul
added a commit
that referenced
this issue
Apr 29, 2015
Fixes #2. Do not commit; requires: jclouds/jclouds#737
gaul
added a commit
that referenced
this issue
Apr 30, 2015
Fixes #2. Do not commit; requires: jclouds/jclouds#737
gaul
added a commit
that referenced
this issue
Apr 30, 2015
Fixes #2. Do not commit; requires: jclouds/jclouds#737
Closed
reluxa
added a commit
to reluxa/s3proxy
that referenced
this issue
Oct 10, 2021
reluxa
added a commit
to reluxa/s3proxy
that referenced
this issue
Oct 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AWS-S3 limits single-part uploads to 5 GB and provides multi-part uploads to allow larger blobs. This API consists of initiate, uploadPart, complete, abort, and listParts. How to translate these multiple calls into the single jclouds method
BlobStore.putBlob(blob, multipart())
? Can S3Proxy provide a dynamicPayload
variant which demuxes these calls?The text was updated successfully, but these errors were encountered: