Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of randall.leeds@gmail.com
 designates 209.85.161.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=ZjpjIS8mwQZVZ/O0S8XElmsKmCmYZ5DT0pmj8pRLY2XDMt9r2bpuNXQ1RBGYNH2q5a
         E2myPxQdxREJEXyWRer4SEx0ua1F6moMYG93bRxakbmZNJknnlhQGRd4yyQjILkW0gpY
         v50fp2ikFimD0QlqSnK7DcVvE1qaBeKVwmdHs=
MIME-Version: 1.0
In-Reply-To: <loom.20110212T200908-106@post.gmane.org>
References: <loom.20110212T200908-106@post.gmane.org>
Date: Sat, 12 Feb 2011 21:42:32 -0800
Message-ID: <AANLkTimvJ1HPgcn-sLrbb1a5bZDaDx1tKU4vgtuimgds@mail.gmail.com>
Subject: Re: CouchDB Replication
From: Randall Leeds <randall.leeds@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 12, 2011 at 11:11, Jim Zombek <jimzombek@verizon.net> wrote:
>
> What is the best way to determine what documents were replicated from sou=
rce to
> target after a sucessfull replication?
>

(Let's try this as plain text)

Good question!

You can do something like this:

@target host
GET /target =3D> {... "update_seq": X, ...}
POST /_replicate {"source": "<source host>/source", "target": "target"} =3D=
> {...}
GET /target/_changes?since=3DX =3D> { //here are your replicated changes }

This last request to /target/_changes will also include any writes to
the target database that occurred between the initial GET and
/_replicate as well as any writes that occurred after the replication
but before the /target/_changes request. If you can only make direct
requests against the target database then it is impossible to
guarantee an exact answer in the presence of concurrent updates to the
target.

On the other hand, if you are performing a push replication from a
local database or can otherwise afford to request changes from the
source after the replication finishes, you can get exactly what you
want even in the presence of concurrent updates to the source and/or
the target using the response body from the replication request.

For push replication:

@source host
POST /_replicate {"source": "source", "target": "<target host>/target"} =3D=
>
=C2=A0 {..., "start_last_seq": A, "end_last_seq": B, ....}
GET /source/_changes?since=3DA&
limit=3DX =3D> { //this is what you want }

where X =3D B - A.

For pull replication:

@target host
POST /_replicate {"source": "<source host>/source", "target": "target"} =3D=
>
=C2=A0 {..., "start_last_seq": A, "end_last_seq": B, ....}

@source host
GET /source/_changes?since=3DA&limit=3DX =3D> { //this is what you want }

where X =3D B - A as above.

Both databases residing on the same host makes the push and pull cases
essentially identical (specifying source and target as both bare
database names [pull] or as both http endpoints [a sort of pull-push
with CouchDB acting as a middleman replication proxy])

Hope that helps.

Randall