GitHub user sagelywizard opened a pull request:
https://github.com/apache/couchdb-fabric/pull/36
Add owner of shard to last_seq of changes response
Prior to this commit, there was a bug where the response of a changes
query would include epoch information for every change, but not for the
last sequence. Subsequent shard changes queries would rewind from zero
if the last_seq field was used in the clustered changes query and any
shard had previously been moved.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloudant/couchdb-fabric 2937-broken-last-seq
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-fabric/pull/36.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #36
----
commit 6d008f61ff10a3d910c3db52fe73439a645f8287
Author: Benjamin Bastian <[email protected]>
Date: 2016-01-20T00:29:34Z
Add owner of shard to last_seq of changes response
Prior to this commit, there was a bug where the response of a changes
query would include epoch information for every change, but not for the
last sequence. Subsequent shard changes queries would rewind from zero
if the last_seq field was used in the clustered changes query and any
shard had previously been moved.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
