Thanks Jan, that article answers a lot of questions. re the following quote: "There is also an option (under development) to immediately return a stale copy of the view in case the client can tolerate that."
My application needs to do hundreds of thousands of index updates for every incoming piece of data, so being able to return a stale result is critical. Where can I find some documentation about this option? Ben On Mon, Oct 27, 2008 at 9:30 AM, Jan Lehnardt <[EMAIL PROTECTED]> wrote: > > On Oct 27, 2008, at 17:15, Dean Landolt wrote: > > On Mon, Oct 27, 2008 at 12:13 PM, Jan Lehnardt <[EMAIL PROTECTED]> wrote: >> >> >>> On Oct 27, 2008, at 16:53, Ben Nevile wrote: >>> >>> >>> First off to alay your main concern, view indexes are not completely >>>>> regenerated on each update. Its only a diff. >>>>> >>>>> >>>>> Presumably reduce operations have to operate on the entire set every >>>> time? >>>> >>>> >>> Nope, reduce results are stored in the btree back nodes. >>> >> >> >> Or...that. >> >> Jan -- can you speak to what that means? Back nodes? >> > > See http://horicky.blogspot.com/2008/10/couchdb-implementation.html > > Cheers > Jan > -- >
