Return-Path: Delivered-To: apmail-incubator-couchdb-user-archive@locus.apache.org Received: (qmail 68364 invoked from network); 25 Jun 2008 12:20:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jun 2008 12:20:54 -0000 Received: (qmail 59433 invoked by uid 500); 25 Jun 2008 12:20:55 -0000 Delivered-To: apmail-incubator-couchdb-user-archive@incubator.apache.org Received: (qmail 59410 invoked by uid 500); 25 Jun 2008 12:20:55 -0000 Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: couchdb-user@incubator.apache.org Delivered-To: mailing list couchdb-user@incubator.apache.org Received: (qmail 59399 invoked by uid 99); 25 Jun 2008 12:20:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jun 2008 05:20:54 -0700 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: local policy) Received: from [85.214.75.170] (HELO busimess.org) (85.214.75.170) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jun 2008 12:20:02 +0000 Received: (qmail 9429 invoked from network); 25 Jun 2008 12:19:18 -0000 Received: from e182035170.adsl.alicedsl.de (HELO ?192.168.1.2?) (mail@kore-nordmann.de@85.182.35.170) by busimess.org with ESMTPA; 25 Jun 2008 12:19:18 -0000 Message-ID: <486237C2.2060405@kore-nordmann.de> Date: Wed, 25 Jun 2008 14:19:14 +0200 From: Kore Nordmann User-Agent: Thunderbird 2.0.0.14 (X11/20080624) MIME-Version: 1.0 To: couchdb-user@incubator.apache.org Subject: Filtered multi-column lists Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi list, I love CouchDB and it is really fun using it, but now I am experience a problem which seems not really solveable properly to me at a first glance using the CouchDB views. I have some amount of documents, which do have several fields in common, which each has some small amount of different values, just like an issue tracker, where you have for example bug type, status and priority for your documents. The amount of documents may be "big" at some point (something between 10^3 and 10^6), so I don't see ad hoc views as a good solution, as the results probably would take too much time to calculate. Also for the amount of fields and their different values it seems not feasible to define a view for each possible combination. I also do not see a real solution in complex keys, like array keys with the provided view values, like [$type, $status, $priority], because afaik it is yet impossible to do queries like [*, (urgent | low), *] or similar. Am I overlooking something here, or isn't there a good solution for such a use case yet? Even I can't find the discussion on the ML now, I remember discussion on XPath-like queries for JSON structures, which could help here for querying the keys of a view, when it holds all the relevant information in its keys - even it may take quite some time to perform such a query against all keys in a view. If there isn't something like this planned yet, and I am not overlooking some kind of obvious solution - do you have some good starting points which could offer a solid base for some evaluation work? -- Kore Nordmann (GPG 0xDDC70BBB) http://kore-nordmann.de/portfolio.html