Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <4568425.36921295362604917.JavaMail.jira@thor>
Date: Tue, 18 Jan 2011 09:56:44 -0500 (EST)
From: "Filipe Manana (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Created: (COUCHDB-1028) Pull replication by doc-IDs, from a
 CouchDB version < 1.1.0, no longer works when sent from a CouchDB 1.1.0+
 server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Pull replication by doc-IDs, from a CouchDB version < 1.1.0, no longer work=
s when sent from a CouchDB 1.1.0+ server
---------------------------------------------------------------------------=
----------------------------------------

                 Key: COUCHDB-1028
                 URL: https://issues.apache.org/jira/browse/COUCHDB-1028
             Project: CouchDB
          Issue Type: Bug
          Components: Replication
    Affects Versions: 1.1
            Reporter: Filipe Manana
            Assignee: Filipe Manana
         Attachments: COUCHDB-1028.patch

After Beno=C3=AEt added the built-in _changes filter _doc_ids to trunk (and=
 now in 1.1.x as well), I updated the replicator to use it for the replicat=
ion by doc-IDs. The advantages of this are:

1) Elimination of very specific, and harder to maintain, code from several =
replicator modules;
2) Allow for continuous by doc-IDs replication (this was not possible befor=
e because a replication by doc-IDs didn't use the _changes stream at all)

The change was done in the following commit:

https://github.com/apache/couchdb/commit/5afece2131f4ef4000d768b671bddbbf71=
4303d9

It happens that with the branch 1.1.x (and trunk as well), it's no longer p=
ossible to pull replicate by doc-IDs from previous CouchDB versions (since =
they don't have that new built-in filter).

The following patch fixes the issue by changing only 1 module of the replic=
ator. If no objections, I'll commit it later.


--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.