couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Lehnardt (Commented) (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1296) _changes style feed for database create/delete
Date Fri, 11 Nov 2011 10:42:52 GMT


Jan Lehnardt commented on COUCHDB-1296:

@Sam my argument is as follows:

A desired feature is to get *all* changes to a server, rather than all changes from a single
Another desired feature is to put the old DbUpdateNotification stdio API on HTTP under say
  Implementing /_db_updates would give you a notification when a db gets any update (i.e.
entry in the _changes feed)
  The client then can monitor /_db_updates and maintain a pool of /$db/_changes requests (that
is updated with /_db_updates) and thus get all changes to a server.
Boom: the first desired feature is solved as well.

The advantages of my approach are that the /_db_updates feed can be used for other things
as well.

> _changes style feed for database create/delete
> ----------------------------------------------
>                 Key: COUCHDB-1296
>                 URL:
>             Project: CouchDB
>          Issue Type: New Feature
>            Reporter: Sam Bisbee
> It would be great to have a _changes style feed for when databases get created and deleted.
Currently if you want to watch the _changes feed or start replication jobs for certain types
of databases (say they're name spaced) you have to get /_all_dbs and then poll it to check
for changes, requiring a full array scan.
> This feed would allow me to hit /_all_dbs once and then get updates without hitting /_all_dbs
every second and scanning a potentially large array.
> Cheers.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message