Hi Jan, thank you for the fast answer, and thanks to Robert for the writeup.
I do have do process changes asynchronously, so a younger change can be already processed before an older change is ready. With 1.x i interpreted the sequence as an ID of the change, with this i could filter the already processed changes and determine the since param to be set to the lowest sequence which wasn't processed yet. With 2.x this isn't possible at all, the sequence for the same change (doc@rev) may differ between calls to _changes, we might see changes multiple times. So the only reasonable way i see is to write back to the processed document, to persist the "is processed" information in the document itself. (If for this particular case it matters whether the same change is processed multiple times). Thanks again, Stefan 2017-10-27 21:08 GMT+02:00 Robert Samuel Newson <[email protected]>: > :blushes: > >> On 27 Oct 2017, at 18:53, Jan Lehnardt <[email protected]> wrote: >> >> Hi Stefan, >> >> this is about as comprehensive as it gets, curtesy of Bob Newson: >> >> https://lists.apache.org/thread.html/aaf94d3e1e67155912e2d68cd584e64366ed34f8f47578a60731afaf@%3Cuser.couchdb.apache.org%3E >> >> Context thread: >> https://lists.apache.org/thread.html/d2f1cf167f931ccb62552b681f44559168755d37b0f51ec1982edbbf@%3Cuser.couchdb.apache.org%3E >> >> Best >> Jan >> -- >> >>> On 27. Oct 2017, at 18:34, Stefan Klein <[email protected]> wrote: >>> >>> Hi, >>> >>> the changes feed Api documentation states that (simplified) the order >>> of changes is not guaranteed and the same seq might show up multiple >>> times. >>> >>> Is there some more documentation on the sequence, the since parameter, >>> how to make sure to actually see the changes I'm interested in? >>> I like to read first before i ask specific questions - if any are left. >>> >>> regards, >>> Stefan >> >> -- >> Professional Support for Apache CouchDB: >> https://neighbourhood.ie/couchdb-support/ >> >
