so... does anyone have an idea why a view can be outdated right after a bulk update?
On Thu, Jan 22, 2015 at 8:30 AM, Boaz Citrin <[email protected]> wrote: > Yep, right after the update, is this an expected behavior? > Can setting *delayed_commits *to true improve/fix this? Can it affect > performance noticeably? > > Thanks! > > > On Wed, Jan 21, 2015 at 11:43 PM, Stanley Iriele <[email protected]> > wrote: > >> Are you calling the view right after?...this is just a thought but they >> may >> not have committed to disk yet at that point >> On Jan 21, 2015 5:33 AM, "Boaz Citrin" <[email protected]> wrote: >> >> > Hello, >> > >> > We are having a strange issue using the bulk document API of couchdb >> 1.2.1; >> > >> > 1. We have a view on a field say 'directory'. >> > 2. We send a bulk update for 50+ documents changing their 'directory' >> > 3. We send a view query with the key being the former directory value >> > 4. Response contains documents that should have been changed. >> > 5. Sending a second request after a fraction gives an empty expected >> > response. >> > >> > Note that we don't query with stale=ok. >> > >> > Any idea? >> > >> > Thanks! >> > >> > Boaz >> > >> > >
