Our specific use case isn't incredibly important, because multi-levelmap-reduce could be useful in countless ways, but I'll include it anyway just as illustration. The specific need for us arose from the desire to slice up certain very large documents to make concurrent editing by a huge number of users feasible. Then we started to use a view step to combine the data back into whole documents. This worked really well at first, but we soon found that we needed to run additional queries on those documents. Sowe were stuck with either:Hey there, Would you mind explaining what those additional queries are? Stephan
In one case, we need to take the combined documents and sort them by
certain metrics (e.g. popularity). There are millions of documents, so
this isn't practical in the client code.
- Re: multi-level views Zachary Zolton
- Re: multi-level views Justin Balthrop
- Re: multi-level views Chris Anderson
- Re: multi-level views Zachary Zolton
- Re: multi-level views Paul Davis
- Re: multi-level views Justin Balthrop
- Re: multi-level views Viacheslav Seledkin
- Re: multi-level views Chris Anderson
- Re: multi-level views Brad Anderson
- Re: multi-level views Stephan Wehner
- Re: multi-level views Justin Balthrop
