[jira] [Commented] (JCLOUDS-894) Expose component operations of multipart upload

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCLOUDS-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004651#comment-15004651 ] 

ASF subversion and git services commented on JCLOUDS-894:
---------------------------------------------------------

Commit 22c789da9eebce8420d098f795ae4249e7608c95 in jclouds's branch refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=22c789d ]

JCLOUDS-894: Use prefix when listing MPU on Swift

Previously we only used the blob name and not the blob
name/slo/timestamp/part size cookie which yield extra parts when
listing an MPU with parts from a previous MPU.  Listing using the
stricter prefix gives the expected results.
Fixes andrewgaul/s3proxy#91.


> 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)