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.
diff --git a/src/fabric_rpc.erl b/src/fabric_rpc.erl
index 057dec3..2554f91 100644
--- a/src/fabric_rpc.erl
+++ b/src/fabric_rpc.erl
@@ -63,10 +63,10 @@
epochs = get_epochs(Db)
},
try
- {ok, #cacc{seq=LastSeq, pending=Pending}} =
+ {ok, #cacc{seq=LastSeq, pending=Pending, epochs=Epochs}} =
couch_db:changes_since(Db, StartSeq, Enum, Opts, Acc0),
rexi:stream_last({complete, [
- {seq, {LastSeq, uuid(Db)}},
+ {seq, {LastSeq, uuid(Db), owner_of(LastSeq, Epochs)}},
{pending, Pending}
]})
after
