Awesome, thanks. Now, to push it a bit further, let's suppose I have three databases in replication : A -> B -> C, and I need to know which document created in A is the last one that got to C, so I can display a "synchronized / not synchronized" symbol next to the various documents in my view.
To know which document got to C, here is my idea: using B's _active_tasks I know which update sequence of B got to C. I query B's _changes feed to know what document/revision that update sequence concerns. I query that same document/revision on A using the local_seq option. Now I know which update sequence of A is the last one that got to C, assuming that* sequences are kept in the same order* through two replications. Is that a safe assumption? Or can anyone think of a simpler way to do this, without having to HEAD each document individually? Foucauld 2015-07-29 17:18 GMT+02:00 Alexander Shorin <[email protected]>: > On Wed, Jul 29, 2015 at 6:13 PM, Foucauld Degeorges <[email protected]> > wrote: > > Just to clarify, by "completed sequence" you mean > checkpointed_source_seq, > > is that right ? > > Yes. This is an update sequence of source which is recorded in > checkpoint what means that all the data up to that value are already > replicated. > > -- > ,,,^..^,,, >
