Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 45938 invoked from network); 28 Aug 2009 20:19:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Aug 2009 20:19:09 -0000 Received: (qmail 93075 invoked by uid 500); 28 Aug 2009 20:19:08 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 93001 invoked by uid 500); 28 Aug 2009 20:19:08 -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 92991 invoked by uid 99); 28 Aug 2009 20:19:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Aug 2009 20:19:08 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of paul.joseph.davis@gmail.com designates 209.85.211.188 as permitted sender) Received: from [209.85.211.188] (HELO mail-yw0-f188.google.com) (209.85.211.188) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Aug 2009 20:19:00 +0000 Received: by ywh26 with SMTP id 26so3125157ywh.5 for ; Fri, 28 Aug 2009 13:18:39 -0700 (PDT) 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; bh=IdRBbfev0IaIKHBN70d8Bg8rJE1W0dvleY0cuhfK/O4=; b=tx23CSYhNXmORCJNYMhCrg3jar20fgTKVhUQyNh9g+8suLoupEpPx5JOvSGZUs8MMK 2L1jTJfXpEiHY9N968wsf/plkmtlNtX85klgoPgRCHCxlPaX6z5SISEP1U+ofQGKtmoy zkLc58xC/uwEWswSHilwxny4QvQZnfw10wI68= 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; b=BWXl7iq8rx6zwbJ4aVdOGiUl2Ht+y0AjePyq1IBi3aF4kctep0QhhhjUa/4rIQt3ws 7Bz8ifFE7XW9bl2c/I/PDn4hhxgGF7i/jflvPmNddhHpqeF7FX3jM+aEbCC8EtnStXJ+ n549WY0NLAgsH1MjnS96rFNA0AEsjsUb5xNF0= MIME-Version: 1.0 Received: by 10.100.236.28 with SMTP id j28mr1713148anh.37.1251490719036; Fri, 28 Aug 2009 13:18:39 -0700 (PDT) In-Reply-To: <2fd53c3a0908281316t44bdaa9av9bf81f5622cabe44@mail.gmail.com> References: <2fd53c3a0908280841v25f03385i39812fd3ef34f6de@mail.gmail.com> <2fd53c3a0908281201la5d22f6u8e46ae0056e79435@mail.gmail.com> <2fd53c3a0908281316t44bdaa9av9bf81f5622cabe44@mail.gmail.com> Date: Fri, 28 Aug 2009 16:18:39 -0400 Message-ID: Subject: Re: 0.9 to 0.10 breaking changes From: Paul Davis To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org > This was my first approach and in general it works for the purpose. > The only problem is when the features are not independent one of each > other. I guess that in that case the only approach is to download all > the [k1, features] and handle them in the client (same problem as > sorting reduce results). Sounds like it. I don't have any other ideas off the top of my head. There's always the possibility of writing an external indexer to do your logic client side if your deployment picture allows for it. HTH, Paul Davis