Bigcouch

[Enome]

I hate asking questions in the issues tab but I was wondering if follow was tested with bigcouch? I am getting some weird results when I try to follow my cloudant db.

[jhs]

Hi, Geert. Follow is not tested on BigCouch however I would love to hear about your problems to try to get them fixed.

On Mon, May 7, 2012 at 6:38 AM, Geert Pasteels reply@reply.github.com wrote:

I hate asking questions in the issues tab but I was wondering if follow was tested with bigcouch? I am getting some weird results when I try to follow my cloudant db.

---

Reply to this email directly or view it on GitHub: https://github.com/iriscouch/follow/issues/15

Iris Couch

[Enome]

Hey jhs, it seems bigcouch has api differences when it comes to changes.

http://bigcouch.cloudant.com/api

• The _changes feed is not totally ordered but does honor all the semantics required for replication and third party synchronization. Two calls to _changes will likely yield a different order of results. There is no guarantee even for a single user that changes made in a certain order will appear that way as writes are distributed to multiple nodes.
• Incremental requests to _changes using the ?since query-string parameter may show the same update multiple times if the set of database partitions used to generate the previous response cannot be contacted; i.e., BigCouch will contact another replica of that partition and merge its local _changes feed into the result instead of refusing the request.

I guess due to the clustered nature of bigcouch they have a somewhat weird _changes feed. Also wonder if I can even use bigcouch for my app because I rely a lot on the changes feed.

Well thanks for the quick answer jhs I do some digging and if something interesting comes up I'll post it here.

[rdzar]

They now accept the ?since=-1 param (by request). But it still doesn't work well. Sometimes it ends after 15 minutes, 30 minutes, 3 hours or 1 day. Completely random without any errors :(

[fkarlsson]

Sorry to revive this old issue! Is anyone working on this one? I'm trying to use follow with Cloudant but has been unable to so far. I thought I'd try to make a patch.

Error I'm getting:

Connection timeout or disconnect, retrying in 1000ms for sequence 5-g1AAAAETeJzLYWBgYMlgTmGQT0lKzi9KdUhJMtbLSs1LLUst0kvOyS9NScwr0ctLLckBKmRKZEiy____f1YGcyJrLlCA3cTYMNUkNYmwdqKtSHIAkkn1IFsSGYjWlccCJBkagBRQ434MnYaEdB6A6ATZmQUA7cFa3Q

And then when it retries I get an unhandled exception:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: stream.push() after EOF
    at readableAddChunk (_stream_readable.js:146:15)
    at IncomingMessage.Readable.push (_stream_readable.js:127:10)
    at HTTPParser.parserOnBody [as onBody] (http.js:142:22)
    at Socket.socketOnData [as ondata] (http.js:1583:20)
    at TCP.onread (net.js:525:27)

I use follow through nano.

[jhs]

I am working on this now, thanks for the ping!

[jcrugzz]

@fkarlsson can you make sure you are running on the latest node version and see if you still get that second error? Not particularly related to using with cloudant but I thought I saw that error disappear in 0.10.28. Cheers!

[sreuter]

@jhs did you make any progress on this? As we're heading "swiftly" towards CouchDB 2.0 (see recent post), it may make sense to tackle this early. I'm also not sure if there are differences between BigCouch and the Cluster-backed API in CouchDB, but will start investigating today.