Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of roddsnook@gmail.com designates
 209.85.223.198 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=qXSaVsWi6aftUG9DYWI7cTt7zdW7GeKjFmr9dWx40k4Nopsnb+Ov9HQMXD9z8eARV8
         Q9pdgrXA/oD/9/tnqgBo5N7kqoKFZNmPm23DkdwzHkxV+mHpszyQrFOttguCPsTxiFb0
         cxOE2i0IZ5vGzYrrsdV8PISOQdqn2vLb+HCCM=
MIME-Version: 1.0
Date: Tue, 9 Feb 2010 10:08:06 +1100
Message-ID: <90f73f241002081508l4892f725va93d4b360f487da8@mail.gmail.com>
Subject: Any experience with partial replication via _changes?
From: Rodd Snook <roddsnook@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=0050450142cabd652c047f1edf2e

--0050450142cabd652c047f1edf2e
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I'm a new CouchDB user in the middle of designing a new publishing
sub-system for a web app. One model that I'm considering is to use a kind of
partial replication, by listening to a filter on _changes, pulling out
documents with a "publish" flag on them and pushing them to a Couch instance
backing up the live site.

Is there anyone with experience doing something similar, who can tell me if
this is an effective strategy, or a recipe for headache and disaster? I'd
link to know ahead of time if there's some pitfall that's going to prevent
me from doing this with a manageably small piece of bash/perl/php.

Rodd

--0050450142cabd652c047f1edf2e--