Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of nicholas.evans@gmail.com
 designates 209.85.216.47 as permitted sender)
MIME-Version: 1.0
Reply-To: nick@ekenosen.net
In-Reply-To: 
 <CACV2Mxd0A7Jii5jc=sHdK5x1CkqANLm6AjaB_9o+R_-sa7GKEg@mail.gmail.com>
References: 
 <CACV2Mxd0A7Jii5jc=sHdK5x1CkqANLm6AjaB_9o+R_-sa7GKEg@mail.gmail.com>
From: "nicholas a. evans" <nicholas.evans@gmail.com>
Date: Tue, 27 Mar 2012 13:12:42 -0400
Message-ID: 
 <CACV2Mxd0_wLYVUntQXktDhqw1SnNZNzXNWq1Fk3gzsN=3oiV4A@mail.gmail.com>
Subject: Re: Sorting CouchDB data using couch-lucene
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 27, 2012 at 1:04 PM, nicholas a. evans
<nicholas.evans@gmail.com> wrote:
> Or is this a
> hammer/screwdriver problem: should we be looking outside of couchdb to
> handle this particular type of data analysis? =A0E.g. monitor the
> changes feed and run "zincrby messages:by_sender 1 $sender" for every
> new row.

Oops.  I forgot to mention that would be a *redis* command.  :)  I'm
not averse to polyglot persistence (we already have redis in our
stack).

--=20
Nick