Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws;
  s=default; d=fto.de;
  b=vb/K9aF6EoqTmOE+SfjilxzOxaQ+UPmiVLjFR//MHAb7LYIV9K4GfJVgDajeQcHKLAyposNeZLqXoxSLavkc/dFeO8S18G8Q8vLO7Nr0Jfb/GoZagrzvllDjX+7ob4pv;
  h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding;
Message-ID: <4CA34CED.6000207@fto.de>
Date: Wed, 29 Sep 2010 16:27:57 +0200
From: Heiko Schaefer <hschaefer@fto.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.1.12) Gecko/20100915 Thunderbird/3.0.8
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Efficient couchdb queries with explicitly specified keyset of >1000
 IDs?
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hello Couchdb-User-List,

I'm building a little family of REST-services with couchdb over the past
months and have made a lot of progress. It's a great experience to get
to know and use couchdb. Right now I'm trying to figure out how to
implement a new requirement - and I feel a little lost.


Here's what I am considering, and would like to know if it sounds at all
feasible:

I expect to have on the order of 100.000 documents in my couchdb, very
soon. But an (independent and external) service may define groups of
documents (a few thousand documents being one group). I'd like to be
able do searches (query couchdb views) on just the subset of documents
that are in one group.
I'm not very keen to mark my documents themselves as members of a group,
if it can be at all avoided. So I thought maybe I can make queries that
explicitly list the relevant few thousand couch IDs in queries.


Example use-case:

There are 100.000 documents in the couchdb. An externally supplied list
specifies a subset of 5.000 IDs.
I'd like to efficiently query a view, but only considering the documents
within this subset of 5.000 IDs. Then I would like to further narrow
down these results by other keys.
[The IDs would probably not map 1:1 onto the couchdb "_id", but rather
onto another field (or two) of the documents]


Would that be as mad (and inefficient) as it sounds? Is there any other
way to achieve my objectives with couchdb that I might be missing?


Sorry if my question is not worded properly or clearly - I don't feel
fluent in the couchdb terminology and way of thinking yet.
Thanks in advance for any help and pointers.

cheers,
:) Heiko