jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Potter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-894) Expose component operations of multipart upload
Date Tue, 21 Jul 2015 15:38:05 GMT

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

Matt Potter commented on JCLOUDS-894:
-------------------------------------

You mentioned enabling parallel uploads w.r.t. this feature.  Will this resolve the problem
getting the ParallelMultipartUploadStrategy to work described in https://issues.apache.org/jira/browse/JCLOUDS-227
?  

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

Mime
View raw message