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)
MIME-Version: 1.0
In-Reply-To: <e2111bbb0901131931y6cdf0e96i4b4e7bb85b1aa9bc@mail.gmail.com>
References: <92fc798f0901131335gbb933cdmdbc0eb7a4c0f70ee@mail.gmail.com>
	 <e282921e0901131338r3ac407c7wb6a9daa15bdc4837@mail.gmail.com>
	 <92fc798f0901131506n43a1fe9cq9e17572dfa2df0f@mail.gmail.com>
	 <e282921e0901131509w5b14114eyab1e4bbc1c645e20@mail.gmail.com>
	 <92fc798f0901131522l7676b0c8m3e40f974b95a19c7@mail.gmail.com>
	 <64a10fff0901131528i3514f3b4qd7a6e68e33f14cb9@mail.gmail.com>
	 <92fc798f0901131544i4e0e9fedx6baac90a2729f0f1@mail.gmail.com>
	 <64a10fff0901131729y1b2289b4ida5e289bb27d151e@mail.gmail.com>
	 <e2111bbb0901131931y6cdf0e96i4b4e7bb85b1aa9bc@mail.gmail.com>
Date: Tue, 13 Jan 2009 22:52:48 -0500
Message-ID: <64a10fff0901131952l3afa21ackd50142e80f7cec32@mail.gmail.com>
Subject: Re: Sort by date and find by key
From: Dean Landolt <dean@deanlandolt.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=0016e64f683afdc3cb04606945d3

--0016e64f683afdc3cb04606945d3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 13, 2009 at 10:31 PM, Paul Davis <paul.joseph.davis@gmail.com>w=
rote:

> On Tue, Jan 13, 2009 at 8:29 PM, Dean Landolt <dean@deanlandolt.com>
> wrote:
> > On Tue, Jan 13, 2009 at 6:44 PM, Nicolas Fouch=E9 <nicolas@silentale.co=
m
> >wrote:
> >
> >> OK, that's what I was thinking. I currently have all my documents in
> >> full-text search indexes. I guess I'll use CouchDB for storage and
> >> some reduce functions to build dashboards, and not for my
> >> "complicated" queries.
> >> I don't want to load my indexes down with the document content. For
> >> more efficiency, they would only contain the reverse indexes.
> >>
> >> As far as I know, the _external process cannot return document ids to
> >> CouchDB, so CouchDB returns the full document to the caller. Would you
> >> recommend doing this on the cliend side ? Query the index, and then
> >> query CouchDB with a bunch of keys ?
> >
> >
> > This is probably a question for Paul D as he's done quite a bit of work
> in
> > this area (and is also working on a pure Erlang FTI as couch plugin). T=
he
> > _external hook returns full docs, sure, but you control the scripts tha=
t
> > pump data into your external indices.
> >
>
> Unless I'm very much mistaken on changes made to the _external code,
> there's nothing that requires you to return full docs whatsoever. The
> complete response can be specified by the OS process. _external is
> extremely shallow in terms of what it requires as a response. You can
> mimic views or do something entirely different with them. For all it
> cares, you could draw mandlebrot fractals in JSON and return that as a
> body.
>
> > But don't forget that couch is more than a db -- it's an app server. It
> > wouldn't hurt to poke around github for some of the pdavis work on this=
.
> You
> > may be surprised with what you could accomplish by using couch as a pro=
xy
> to
> > and interface for other query mechanisms. Also, I'm pretty sure some of
> this
> > FI stuff is set for inclusion by 1.0, which is nice.
> >
>

Sorry about that, I was making an assumption -- I haven't played too much
with it. That was meant to come out "maybe _external requires..." though,
now that I think about it I'd have known that was wrong if I'd just thought
about it.

In any event, all I was trying to say was that there's a lot more to
interacting with external processes than just some DBUpdateNotification
ability to do it.

--0016e64f683afdc3cb04606945d3--