New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replication - when doc_ids is defined the changes feed is dependent on batch_size #2426
Comments
It's a bug, we look for a batch with nothing in it to know when replication
|
doc_ids are not passed to the changes feed used in the replicator. This generates unnecessary overhead, since every change in the db is passed through the changes feed used by the replicator. |
@wendall911 Are you sure? Line 472 in a8c8624
|
@nolanlawson Yes, I'm sure. The underlying _changes does not make use of doc_ids, so this is only a client-side filter at this point. |
So I figured this behaviour has likely changed over 2 years, it looks to be working now and added a test to verify @ #5254 |
If a couchDB database has more than 100 documents and the specified ids in doc_ids exists beyond those first 100 then the documents specified will not replicate since the changes feed with only check up until the amount specified by the batch_size which defaults to 100.
So assuming couchDB database with
500 documents
and IDs as
001,002,003,....498.499,500
This will not replicate any documents.
Unless batch_size is defined as the total size of the database it will only check the first 100.
This will replicate all three documents with the IDs
'101','201','301'.
I think this is a fairly specific use case and this might be intentional because of that.
The text was updated successfully, but these errors were encountered: