nickva commented on issue #5200: URL: https://github.com/apache/couchdb/issues/5200#issuecomment-2306341384
After 256 rows are emitted, because of the `feed=continuous` parameter, it will wait until the default timeout expires (60 seconds it seems). Yeah, that is a bit of odd behavior. It seems if we emitted >= limit rows, we could end the request early, despite the timeout. [Docs say](https://docs.couchdb.org/en/stable/api/database/changes.html#continuous): > A continuous feed stays open and connected to the database until explicitly closed and changes are sent to the client as they happen, i.e. in near real-time. but also > If limit has been specified the feed will end with a { last_seq } object. Continuous seems to take precedence regardless of limit I guess in general it may be possible to control the time it will keep waiting with an explicit `timeout=$msec` parameter: ``` curl http://127.0.0.1:5984/myDb/_changes`?feed=continouos&limit=256&timeout=5000` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
