[
https://issues.apache.org/jira/browse/JCLOUDS-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Gaul resolved JCLOUDS-894.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Declaring victory, having exposed the component operations on Azure, GCS, S3,
and Swift and moving from custom strategies into a common one. Note that I did
not port Glacier and the legacy Swift provider.
> 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
> Fix For: 2.0.0
>
>
> 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)
