Hi, which version of Couchbase are you using? 3.0?
If you want to make sure the items shows up in the view, you would request the view with the stale=false parameter.
Please note note that you should be careful with stale=false requests. If you do them very frequently, it will blow up the on disk size of the views and compaction will be triggered quite frequently. It's better to do stale=ok requests and only stale=false when really needed.
Cheers, Volker On 10/24/2014 12:08 AM, atedja.nm wrote:
I am using the Ruby's Couchbase client libarary. I did a simple test, inserting a new record by using the #set method. I can immediately retrieve it by calling #get. That's fine. However, if I retrieve the object through a view, I can't do it instantaneously. It's like there's a delay of a second. So, I'm curious how long Couchbase takes to index the view whenever there's insertion/updates. This is running off a test bucket, which only has 128MB RAM. Also observable on a bucket that has 512MB. I don't know if it has something to do with the RAM. Is there a way to minimize this effect? -- 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] <mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout.
-- 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.
