Return-Path: 
 <commits-return-6290-apmail-libcloud-commits-archive=libcloud.apache.org@libcloud.apache.org>
X-Original-To: apmail-libcloud-commits-archive@www.apache.org
Delivered-To: apmail-libcloud-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id B33F210B5D
	for <apmail-libcloud-commits-archive@www.apache.org>;
 Mon,  6 Jan 2014 01:12:50 +0000 (UTC)
Received: (qmail 17876 invoked by uid 500); 6 Jan 2014 01:12:50 -0000
Delivered-To: apmail-libcloud-commits-archive@libcloud.apache.org
Received: (qmail 17852 invoked by uid 500); 6 Jan 2014 01:12:50 -0000
Mailing-List: contact commits-help@libcloud.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@libcloud.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@libcloud.apache.org>
List-Post: <mailto:commits@libcloud.apache.org>
List-Id: <commits.libcloud.apache.org>
Reply-To: dev@libcloud.apache.org
Delivered-To: mailing list commits@libcloud.apache.org
Received: (qmail 17844 invoked by uid 99); 6 Jan 2014 01:12:50 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jan 2014 01:12:50 +0000
Date: Mon, 6 Jan 2014 01:12:50 +0000 (UTC)
From: "Tomaz Muraus (JIRA)" <jira@apache.org>
To: commits@libcloud.apache.org
Message-ID: <JIRA.12687377.1388969508963.45195.1388970770601@arcas>
In-Reply-To: <JIRA.12687377.1388969508963@arcas>
References: <JIRA.12687377.1388969508963@arcas>
Subject: [jira] [Commented] (LIBCLOUD-490) Zero-byte uploads to S3 fail
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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