Skip to content
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

Support for CBLReplication.pendingDocumentIds #473

Closed
pasin opened this issue Jul 30, 2015 · 4 comments
Closed

Support for CBLReplication.pendingDocumentIds #473

pasin opened this issue Jul 30, 2015 · 4 comments
Milestone

Comments

@pasin
Copy link
Contributor

pasin commented Jul 30, 2015

This feature has been implemented in iOS and was recently fixed to return the result even when the replication is not running. It's returned the document ids that haven't been pushed to the server.

Issue: couchbase/couchbase-lite-ios#807

@Steven-Mark-Ford
Copy link

Steven-Mark-Ford commented Aug 11, 2016

I always get a null list when calling GetPendingDocumentIDs() on pull replication object. I took a look at the source and it seems _pendingDocumentIDs is never set in the case of a pull due to guard clause at the beginning of the GetPendingDocumentIDs method.

You can see comment on source here: 1335608#diff-a2278ba36f77f34edb5e51d38ad8fd4aR695

@borrrden
Copy link
Member

That's by design. This property is not supported for pull because the information is not available in the same way that it is for push.

@Steven-Mark-Ford
Copy link

Thanks. Do you know if there is any way currently to get the number of pending docs remaining to pull or if this is something that may be available in a future release? even if its a manually http request to SG.

@borrrden
Copy link
Member

There are no plans for this functionality on either the cloud side or the client side. The problem is the question "pending docs remaining for whom?". Each replication, each user, each role has a different list of pending documents and they are calculated on demand and then streamed to the client. If you can emulate the same call the _changes on Sync Gateway then you will be able to get the same information but be warned that this is a fairly expensive operation for Sync Gateway. If you'd like to continue discussing this, however, consider using our forums so that other people can easily find it for reference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants