u can listen to and filter the doc-changes feed and only re-apply the "delete" ops to chainedDB... in parralel to the other stuff. Combination might not be immediately consistent but will become one... eventually
have fun On Wed, 12 Dec 2012 16:55:05 -0500 "nicholas a. evans" <[email protected]> wrote: > On Wed, Dec 12, 2012 at 4:22 PM, svilen <[email protected]> wrote: > > i dont know if it can help, but i found that u can include > > local_seq=true in the view options, and that will expose > > doc._local_seq as the last change# of the doc. which eventualy > > can skip some steps below.. > > Thanks. I had completely forgotten about that feature. It looks like > it would simplify my "modified incremental" approach... unfortunately, > on further analysis my modified incremental approach is suffering one > major flaw: it can't delete *missing* view rows. Using local_seq > would make it easier to find updated view rows, but would still not be > able to detect missing view rows. The (slow, naive) update > *everything* and three-db-couch-incarnate approaches seem to be the > only way to incrementally delete missing view rows from the chained > DB. Or a view changes feed. > > -- > Nick
