On Tue, Mar 11, 2014 at 11:46 AM, Matt Ingenthron <[email protected]>wrote:
> Hi all, > > While Couchbase Server has great, flexible incremental Map-Reduce with > the views feature, developers often express a desire for a way to more > simply operate with a range of documents/items directly. Usually, this is > by getting, touching or deleting a range. > > To that end, I've posted a DRAFT > proposal<http://www.couchbase.com/wiki/display/couchbase/Project+Left+Ranger>for > some new range operations. It's only a draft at the moment, but I > would like to get feedback from anyone who may have a need for this. From > the summary: > > This project will extend the system to allow for range operations. It > will specifically add support for range queries which will also consider > incoming changes that match that same range while the range query is being > executed. > > > Posting comments to the wiki there or this thread would be greatly > appreciated! > Very interesting. What's most unclear especially if you compare it to couchdb's _all_docs is whether this will be limited to single vbucket or not. If it's limited to single vbucket then it's not as useful as _all_docs (unless we also deploy long due client-side extension to control sharding of docs into vbuckets). If it's across all vbuckets (like poor and "gonna die" _all_docs implementation of couchbase is doing) then it's risking to be too slow. BTW there's http://www.couchbase.com/issues/browse/MB-10034 with some context on very similar requirement for document editing UI. -- You received this message because you are subscribed to the Google Groups "Couchbase" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
