Hi Santhosh, >From the diagram, it appears your flow requires a consistent view between RAM and Disk. I don't know sufficient detail from the diagram, but I can give a general answer.
In 2.x, the way to accomplish this consistency is to Observe() the SET to ensure it is on disk, and then issue a stale=false query to View. In 3.x, it is not necessary to do Observe; Views engine stale=false will pick up all changes from RAM directly. Best Regards, Sriram On Thursday, April 23, 2015 at 1:20:03 PM UTC+5:30, SANTHOSH KUMAR S wrote: > > Hi All, > > We have an issue with respect to couch base where multiple bookings are > happening for the same seat as we are using a couchbase view. > > Attached Time Space Diagram for analysis. > > Please provide your thoughts. Will update more information as we proceed. > > Thanks, > Santhosh > -- 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.
