On Thu, Oct 13, 2016 at 11:02 AM, Jens Alfke <j...@couchbase.com> wrote:
> Right; IIRC this is because you’re using a filter function on CouchDB,
> which scales poorly because every document has to be passed through a
Yes, That seems to be a problem , even with filters written in Erlang
(Sidenote: Ive posted a SO question indicating filters in JS/Erlang as the
> The problem is that for Step 4 above, there is no way to pass in a "since"
> parameter to the _changes feed. The Native API doesnt seem to have a way to
> feed in the since parameter.
> I think what you’re saying is that there’s no way to pass a remote “since”
> value to the *replicator*, i.e. a checkpoint to start from. This is true.
> The only case where you might need it is if you’re trying to halfway
> replace the replicator, as you’re doing, and I don’t think this is
> something we can provide support for. The replicator is pretty intricate,
> and we have enough support issues without exposing more parameters that
> could mess up its state… :/
> It’s also worth pointing out [if I haven’t already!] that the ‘channels’
> mechanism in Sync Gateway was designed explicitly to get around this
> scalability problem in CouchDB.
@tleyden suggested in another thread the same thing, Ill try and see if the
above solution is bearable, otherwise will have to shift to using Channels
and Sync Gateway.
You received this message because you are subscribed to the Google Groups
"Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.