From user-return-3523-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Thu Feb 12 16:16:33 2009 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 81462 invoked from network); 12 Feb 2009 16:16:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Feb 2009 16:16:33 -0000 Received: (qmail 84934 invoked by uid 500); 12 Feb 2009 16:16:31 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 84909 invoked by uid 500); 12 Feb 2009 16:16:31 -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 84898 invoked by uid 99); 12 Feb 2009 16:16:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2009 08:16:31 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kerr.rainey@gmail.com designates 209.85.218.163 as permitted sender) Received: from [209.85.218.163] (HELO mail-bw0-f163.google.com) (209.85.218.163) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2009 16:16:23 +0000 Received: by bwz7 with SMTP id 7so1203146bwz.11 for ; Thu, 12 Feb 2009 08:16:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=9NOaG8Ujt1rp8q3ecAb8+Y3Q3WKQEkJXd4+skUJPqPE=; b=WlmzYN2WtewpAFMRK8rBKz3NZJtJZxFw01a1g1Q9DUgLA99AHkFxJm3IXiad+Em9O1 I2rKECzUGgjx5dg0g5JObi8jY6mcEl3rbLfcR05NftuZtGmSBTJNt0I7L9zXFOA7OwdE uWykzwMw2rR912VPwGkEzOBMH/asaqPeFsQXQ= 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=ZsLseEfe+i5MNdXR31cllw89LWdEW/ijV7f1vk3HI9DrcUXOjQ7vIGFbnR1LBkOV+D lrLcpVAEx0huAtm++rgXDfxO4kSAY4QcE7/nkdb722NjmjcH7qAr/JeqCHw86rNL2dT2 h7Qu0KhFEeX++Z1I97bRVra3SzaxzDz5IysBw= MIME-Version: 1.0 Received: by 10.86.99.9 with SMTP id w9mr1525170fgb.12.1234455362616; Thu, 12 Feb 2009 08:16:02 -0800 (PST) In-Reply-To: <64a10fff0902120805l70905938u2ee8ea285e3fb26e@mail.gmail.com> References: <4b307fd10902120242v3bbbc93fs92c88503eb632fe9@mail.gmail.com> <64a10fff0902120746j187aff2bpc1e5585b32007497@mail.gmail.com> <5e6458d0902120759r24d7010evef257a4674d94187@mail.gmail.com> <64a10fff0902120805l70905938u2ee8ea285e3fb26e@mail.gmail.com> Date: Thu, 12 Feb 2009 16:16:02 +0000 Message-ID: <5e6458d0902120816u3547b3caxd997890308b7268f@mail.gmail.com> Subject: Re: playing with tags From: Kerr Rainey To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 2009/2/12 Dean Landolt : > Perhaps in this scenario, but take a feed reader, for instance. When a user > is tagging feeds, it is subject to change at a much different rate than the > otherwise static content. Even in a single user scenario, once replication > is introduced (say, to a local instance of the app), it's easy to imagine a > situation where things get messy. Then imagine read/unread metadata, and all > the others types of user data associated with this otherwise static content. Obviously you need to fit the solution to the problem. Storing meta data in a doc is not inherently a problem. Storing *any* data that has high contention on a single document is a problem, but that's just basic CouchDB in the same way that you wouldn't store the comments on a single blog post doc. If your meta data is highly contended then you need to find another way round it. But all this is a non sequitur from the problem of getting AND semantics for keys in view lookups. -- Kerr