[
https://issues.apache.org/jira/browse/JCLOUDS-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576622#comment-14576622
]
ASF subversion and git services commented on JCLOUDS-894:
---------------------------------------------------------
Commit 04c4d5c916eee9fc54e0ae867a997bcda5e28032 in jclouds's branch
refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=04c4d5c ]
JCLOUDS-894: Odds and ends for other providers
> Expose component operations of multipart upload
> -----------------------------------------------
>
> Key: JCLOUDS-894
> URL: https://issues.apache.org/jira/browse/JCLOUDS-894
> Project: jclouds
> Issue Type: New Feature
> Components: jclouds-blobstore
> Affects Versions: 1.9.0
> Reporter: Andrew Gaul
> Assignee: Andrew Gaul
> Labels: multipart
>
> Presently jclouds exposes multipart upload via a simple interface:
> {code:java}
> blobStore.putBlob(containerName, blob, new PutOptions().multipart(true));
> {code}
> This does not allow more complicated interactions such as parallel uploads,
> uploads with unknown content-lengths, and other interfaces like writing into
> an {{OutputStream}}. Further the current {{MultipartUploadStrategy}}
> implementations duplicate code across the azureblob, gcs, and s3 providers.
> I propose to expose the MPU component operations, e.g., initiate, complete,
> abort, and upload part, via the {{BlobStore}} abstraction. This will allow
> us to address all the above features.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
