Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 66826 invoked from network); 25 Nov 2010 17:17:54 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 25 Nov 2010 17:17:54 -0000 Received: (qmail 76167 invoked by uid 500); 25 Nov 2010 17:17:52 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 76015 invoked by uid 500); 25 Nov 2010 17:17:52 -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 76007 invoked by uid 99); 25 Nov 2010 17:17:51 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Nov 2010 17:17:51 +0000 X-ASF-Spam-Status: No, hits=3.6 required=10.0 tests=FREEMAIL_FROM,FS_REPLICA,RCVD_IN_DNSWL_NONE,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of st.fankl.in@googlemail.com designates 209.85.161.52 as permitted sender) Received: from [209.85.161.52] (HELO mail-fx0-f52.google.com) (209.85.161.52) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Nov 2010 17:17:45 +0000 Received: by fxm5 with SMTP id 5so961761fxm.11 for ; Thu, 25 Nov 2010 09:17:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=zdAYtTgoMVT8Loa/CjaTp5sIiNAhvjD+8uh1O1Vwmuw=; b=Xrpzm347HpGaKtLoLhYQoQZm1kivt98k0Y+7QJlGaEOCgmxL+GE3nIxDqdIIQdQzYe SCC2CMzFAsVcMyYztSuPEq+pbSprHyn72Ez8uTG3c+eKwKIZ4wN2Paz52fv3iXov2bod gk07lNmt4kaiGf8yO/Q9n5qEh8Kr6eq9WwD2s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=GczYsuBkLw6MTIhNsY7c0kqMfcPDr3eEi6usLuNHEfAtzsMypO1Qhut1KN+uDC+KMi 6m7fIZ47vPEPrQ/29wRlHiKgxCIKptuLlNjj5eAh1C5VsjFpv/XeJnqUFeYQLZ3UR+/w KonxFHEC8hVwxSiH5pilavncShHuGAjgbcTTA= Received: by 10.223.93.133 with SMTP id v5mr1005263fam.119.1290705444339; Thu, 25 Nov 2010 09:17:24 -0800 (PST) Received: from [192.168.1.101] (p4FC0F23E.dip.t-dialin.net [79.192.242.62]) by mx.google.com with ESMTPS id l14sm255519fan.9.2010.11.25.09.17.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 25 Nov 2010 09:17:23 -0800 (PST) Message-ID: <4CEE9A21.3030601@googlemail.com> Date: Thu, 25 Nov 2010 18:17:21 +0100 From: Stefan Klein User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: user@couchdb.apache.org Subject: Replication and filters, deletion of documents Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Hi List, is it possible to filter out deleted documents for replication? If you have 2 database, one holding all documents (db1), the other only a subset (db2). As I understand replication you can have a filtered replication from db1 to db2 and a non filtered from db2 to db1. What happens to a document if once was replicated on a later replication cycle doesn't fit the filter criteria any more? Is it possible to delete documents on db2 and don't replicate this deletion back to db1? regards, Stefan