Thanks for the suggestion. The solution was based not considering other indexing server other than the standard view, but I got curious to see the integration with lucene, considering also that a full-text index can be really helpful.
Configuring couchdb-lucene was quite simple, but I got unexpected results on some of the queries. I have documented it in this gist: https://gist.github.com/fe0fcf29cb38e7df23d1 Is the function described the best way to index an array of tags? Thanks, -- Amedeo On Thu, Feb 10, 2011 at 17:11, Robert Newson <[email protected]>wrote: > couchdb-lucene is an alternative to the combinatorial explosion approach; > > https://github.com/rnewson/couchdb-lucene > > B. > > On 10 February 2011 15:57, Zachary Zolton <[email protected]> > wrote: > > Amedeo, > > > > If you can afford the disk space, it's a fair tradeoff. I've used a > > similar strategy in the past, and it worked out well for me. > > > > You may want to consider limiting the maximum size of tag combinations > > to index. For example, I changed my view to emit tag combination > > arrays with no more than 4 elements. This could significantly reduced > > the index size if your documents have many tags. > > > > > > Cheers, > > > > Zach > > > > > > On Thu, Feb 10, 2011 at 9:29 AM, Amedeo Paglione > > <[email protected]> wrote: > >> Hi all, > >> > >> I have been playing with CouchDB for a while and I had to address the > >> problem of retrieving documents which match a list of tags. > >> > >> I have documented my approach here: > >> > >> https://gist.github.com/820412 > >> > >> It is working, but I am wondering what could be an alternative and more > >> efficient solution to this problem. > >> > >> Regards, > >> -- > >> Amedeo > >> > > >
