Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 559A5D091 for ; Sun, 9 Sep 2012 22:17:10 +0000 (UTC) Received: (qmail 58725 invoked by uid 500); 9 Sep 2012 22:17:08 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 58689 invoked by uid 500); 9 Sep 2012 22:17:08 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 58680 invoked by uid 99); 9 Sep 2012 22:17:08 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Sep 2012 22:17:08 +0000 Received: from localhost (HELO [192.168.1.5]) (127.0.0.1) (smtp-auth username rnewson, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Sun, 09 Sep 2012 22:17:08 +0000 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Apple Message framework v1278) Subject: Re: Any way to upload a revision in pieces? From: Robert Newson In-Reply-To: <18163B96-A0D9-466F-8C72-1C3785FB36E6@apache.org> Date: Sun, 9 Sep 2012 23:17:06 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <6A39682F-121C-4680-A4AA-E9AA14F2E235@apache.org> References: <5BFA6443-8E2A-4884-88F0-1837C29FA0F3@apache.org> <9605FB4F-BA93-43D7-9FAB-9F941AFEB23E@couchbase.com> <18163B96-A0D9-466F-8C72-1C3785FB36E6@apache.org> To: user@couchdb.apache.org X-Mailer: Apple Mail (2.1278) fwiw, I uploaded a 150mb attachment to my cloudant account no problem. = Perhaps I need larger attachments or multiple? On 9 Sep 2012, at 23:00, Robert Newson wrote: >=20 > I'm saying that multipart/related uploads should allow attachments = considerably larger than 64 mb. The limit, on Cloudant, should be = available disk space in the cluster and your budget, since disk usage is = part of the metered service. >=20 > =46rom what I've read here and elsewhere, this is probably more like a = bug in the clustering code for attachment stream (since we fork the = stream during the request to make 3 copies of it) and/or a timeout in = the load balancing layer. >=20 > This is something I'd like to see fixed (assuming I'm right in that = last paragraph) and it sounds easy to reproduce. >=20 > B. >=20 > On 9 Sep 2012, at 22:36, Jens Alfke wrote: >=20 >>=20 >> On Sep 9, 2012, at 2:28 PM, Robert Newson wrote: >>=20 >>> No, there's no way to do that, since a document must change from one = revision to another atomically. >>=20 >> That=92s what I thought. >>=20 >>> The CouchDB replicator uses multipart/related PUT to send the = document and all attachments (streamed) in a single request. The = max_document_size (4gb, insanely, in couchdb, 64mb on cloudant) does not = apply to streamed attachments or the multipart/related PUT method. It = seems like you're asserting that TouchDB doesn't follow suit, which = would surprise me. >>=20 >> TouchDB=92s replicator uploads docs with attachments in MIME = multipart/related format. But Cloudant is rejecting them anyway. Are you = saying it ought to be allowing HTTP uploads of arbitrary size as long as = the main JSON doc is < 64MB? Because that isn=92t what's happening. >>=20 >> =97Jens >=20