Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Filtered replication and separate design documents
From: Jan Lehnardt <jan@apache.org>
In-Reply-To: <BE872B14-E4BB-4FBD-948C-943D4BB5DC90@vpro.nl>
Date: Fri, 28 Jan 2011 12:17:51 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA2E3BC3-57F1-433B-8EF3-32F42BF6C703@apache.org>
References: <BE872B14-E4BB-4FBD-948C-943D4BB5DC90@vpro.nl>
To: user@couchdb.apache.org


On 28 Jan 2011, at 11:52, Nils Breunese wrote:

> Hello,
>=20
> We're researching a CouchDB setup involving a master CouchDB which has =
a database with a complete dataset and several other CouchDB instances =
which should all receive their own subset of the master database. I =
believe this is possible using filtered replication [0]. What we're =
wondering is this: is it possible for the non-master CouchDB databases =
to manage their own design documents separately from the master CouchDB? =
They should get their documents from the master CouchDB via filtered =
replication, but want to be able to have their own custom views. Is this =
possible?

Yup :) =97 The replication target databases on the clients are just =
regular databases under the full control of the client. You will be able =
to add new design docs or alter the existing ones to your need (I'd go =
with the former in case the master updates its design docs to avoid =
conflicts).

I hope this answers your question.

Cheers
Jan
--=20

>=20
> Nils.
>=20
> [0] http://wiki.apache.org/couchdb/Replication#Filtered_Replication
> =
------------------------------------------------------------------------
> VPRO   www.vpro.nl
> =
------------------------------------------------------------------------