[GitHub] kdoran opened a new issue #1221: `_changes` filtered on `_doc_ids` returns unexpected `last_seq`

[GitBox <gi...@apache.org>]

kdoran opened a new issue #1221: `_changes` filtered on `_doc_ids` returns unexpected `last_seq`
URL: https://github.com/apache/couchdb/issues/1221
 
 
   ## Expected Behavior
   From: http://docs.couchdb.org/en/2.1.1/api/database/changes.html#post--db-_changes:
   
   > "last_seq is the update sequence of the last update returned (Equivalent to the last item in the results)."
   
   When filtering on `_doc_ids`, I was expecting `last_seq` to be the same thing as the last `seq` in the list of changes returned when filtering on _doc_ids.
   
   ## Current Behavior
   When filtering on `_doc_ids`, `_changes` responds with the latest sequence in the database or, if there's a `limit` argument, the sequence number after the limit number.
   
   ## Steps to Reproduce (for bugs)
   1. `POST /{db}/_changes?filter=_doc_ids&since=0` with body `{doc_ids: ['one-example-id']}`
   2. See that `last_seq` in response is not the last `seq` in the list of changes.
   
   ## Context
   Grabbing the `last_seq` from the `_changes` response and using it as the `since` parameter on the next request to `_changes` is PouchDB's approach to a replication filtered on IDs. Using that later sequence number means documents are (sometimes) missed in the replication. 
   
   https://github.com/pouchdb/pouchdb/issues/6809
   
   ## Your Environment
   Saw this when running a single node CouchDB 2.1 & on CouchDB 1.6 locally on a macbook pro.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services