tree e85f1abd74b4f8868521e83aeb5900ac7848ad1b
parent c38c692fcf0b8b69f94109ead3c5370144090f8f
author Paul J. Davis <paul.joseph.davis@gmail.com> 1423626580 -0600
committer ILYA Khlopotov <iilyak@ca.ibm.com> 1468264939 -0700

Use the correct sequence for shard replacement

The call to unpack the since sequence for _changes incorrectly filtered
the value for any shard that didn't exist. This means that any shard
that was moved ended up requiring a complete rescan which is a bug. This
just sets the update sequence to the range of the shard being replaced
rather than zero.

COUCHDB-3055