You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@couchdb.apache.org by gi...@git.apache.org on 2017/08/11 17:01:39 UTC

[GitHub] wohali commented on issue #748: Different last_seq when calling changes, with a limit

wohali commented on issue #748: Different last_seq when calling changes, with a limit
URL: https://github.com/apache/couchdb/issues/748#issuecomment-321866164
 
 
   This is normal for a sharded cluster of CouchDB nodes. The actual last_seq returned in CouchDB 2.x contains additional information, including which shard/node in the system you are talking to.
   
   You should treat the _changes token as opaque.
 
----------------------------------------------------------------
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