jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-801) AWS S3 Multipart upload does not work with InputStream payload
Date Sat, 10 Jan 2015 06:02:34 GMT

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

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

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

JCLOUDS-801: Use Iterable payload slicer for AWS-S3

Payload slicer has a method that returns an iterable of payloads that
works on non-repeatable InputStreams that was introduced to fix
multi-part uploads in Swift (JCLOUDS-356). This commit applies the
same method to fix multi-part uploads for AWS-S3 blob store.


> AWS S3 Multipart upload does not work with InputStream payload
> --------------------------------------------------------------
>
>                 Key: JCLOUDS-801
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-801
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.8.0, 1.8.1
>            Reporter: Richard Nichols
>            Assignee: Andrew Gaul
>
> These was previously fixed in JCLOUDS-356 but no longer works.
> Based on my analysis of the code, this is because SequentialMultipartUploadStrategy no
longer calls Payload.slice(...) returning Iterable<Payload> but instead calls the same
returning Payload for an offset and length. This will not work with a non-repeatable InputStream.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message