libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomaz Muraus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-490) Zero-byte uploads to S3 fail
Date Mon, 06 Jan 2014 01:12:50 GMT

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

Tomaz Muraus commented on LIBCLOUD-490:
---------------------------------------

[~mahendra.m] Can you please look into this one?

It looks like a bug which happens when you try to upload a zero byte object using multipart
upload. I thought we've fixed this as part of LIBCLOUD-378, but this doesn't appear to be
the case (or maybe it's just an edge case which only happens for zero bytes sized objects?).

Ideally (like we've talked in the past), we could avoid multipart upload stuff altogether
if the whole file is smaller than a minimum chunk size (5 MB). I know that because the way
code currently works, this might be easier said then done.

> Zero-byte uploads to S3 fail
> ----------------------------
>
>                 Key: LIBCLOUD-490
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-490
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Storage
>    Affects Versions: 0.13.3
>            Reporter: Noah Kantrowitz
>
> Calling storage.upload_object_via_stream(iter(('',)), path) fails with:
> {{libcloud.common.types.LibcloudError: <LibcloudError in <libcloud.storage.drivers.s3.S3StorageDriver
object at 0x10b786610> 'Error in multipart commit'>}}
> A workaround is temporarily monkeypatch {{S3StorageDriver.supports_s3_multipart_upload
= False}}. It would be nice if I could just call put_object directly in some useful way, for
data that is small enough to fit in RAM (which in the case of an empty file is a bit of a
tautology).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message