From user-return-13630-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Wed Nov 10 13:08:58 2010 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 5264 invoked from network); 10 Nov 2010 13:08:58 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 10 Nov 2010 13:08:58 -0000 Received: (qmail 35180 invoked by uid 500); 10 Nov 2010 13:09:28 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 34970 invoked by uid 500); 10 Nov 2010 13:09:24 -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 34953 invoked by uid 99); 10 Nov 2010 13:09:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Nov 2010 13:09:23 +0000 X-ASF-Spam-Status: No, hits=3.6 required=10.0 tests=FREEMAIL_FROM,FS_REPLICA,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of fdmanana@gmail.com designates 209.85.214.52 as permitted sender) Received: from [209.85.214.52] (HELO mail-bw0-f52.google.com) (209.85.214.52) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Nov 2010 13:09:18 +0000 Received: by bwz4 with SMTP id 4so671271bwz.11 for ; Wed, 10 Nov 2010 05:08:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=A9q+dlth7tRwErdpnVM7gpMJNXrExbkdCpao6BZ7pdI=; b=pb4eFilqEyf3PpbcfSkj45zkh5QlyQ1YxOgBgGoHWV3K6ehQt4a2aDRVmjPHDjo7QL kBreJvOulKV8w+4GN4RsA5Ll+6z39BmxfaimxTmW7bm7dy3/VR+4+lbrFzdfLY6hRsno A4Fv8+ZWZssQx1pgfF5PImHzKdkul4/lMuJmg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=ippcJP2mVgD/4ix5hU6ng2ktB/NoUP79/1l3NAoUVrCCHNrV/gr7ZB7aqhdxqhR8oW M0UqyydRByXwiy7Xk5klRLmvq9gL528AzspkfoH3MtMLqqy7BtvmbhYtQQx+1UCSV6V5 NOD2qYN5RJbu5AbJ31yUBwAlm3qVspMihLUaY= MIME-Version: 1.0 Received: by 10.204.68.136 with SMTP id v8mr7758390bki.188.1289394537288; Wed, 10 Nov 2010 05:08:57 -0800 (PST) Sender: fdmanana@gmail.com Received: by 10.223.96.143 with HTTP; Wed, 10 Nov 2010 05:08:57 -0800 (PST) In-Reply-To: <7A7DC524-29B1-4010-B58B-1AD0EE2D0177@meshbrains.com> References: <7A7DC524-29B1-4010-B58B-1AD0EE2D0177@meshbrains.com> Date: Wed, 10 Nov 2010 13:08:57 +0000 X-Google-Sender-Auth: LjrBakS1sHG5fi15bERwYYsAamk Message-ID: Subject: Re: Replicating lots of large attachments From: Filipe David Manana To: user@couchdb.apache.org Cc: scott@meshbrains.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Scott On Sat, Oct 30, 2010 at 9:51 PM, scott wrote: > Hopefully a simple architecture question... > > I have hundreds of laptop users that need to replicate hundreds of PDFs > with several hundred pages each. > > For each PDF, I create a document with it as an inline attachment... > everything is fine. > If I later edit or add a field, maybe to many of the documents, the entir= e > document (or > documents) get replicated. There's a new replicator being developed for some time now (Damien started it, and I resumed his work). This new replicator no longer does that. It only transfer attachments that are not already in the target database. Right now it's unstable (specially for pull replications). I expect it to be close very close to finished within 1 or 2 weeks. Ping me if I forget to let you know when to test it for your use case. regargs, > > This discourages me from editing the meta info for each document as I kno= w > it's > going to create a large replication task for such small updates. > > Is it better to create (for each PDF), say a standalone attachment, with > minimal > fields (just enough to identify it). And then create another associated > document that > contains more rich meta information that may change quite a bit? Smells a > little > kludgy. > > Or is there a better way to handle this? > > Thanks a bunch... > --=20 Filipe David Manana, fdmanana@gmail.com, fdmanana@apache.org "Reasonable men adapt themselves to the world. =C2=A0Unreasonable men adapt the world to themselves. =C2=A0That's why all progress depends on unreasonable men."