From dev-return-19206-apmail-couchdb-dev-archive=couchdb.apache.org@couchdb.apache.org Fri Nov 11 10:43:16 2011 Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7F2EB7D1C for ; Fri, 11 Nov 2011 10:43:16 +0000 (UTC) Received: (qmail 32162 invoked by uid 500); 11 Nov 2011 10:43:15 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 32131 invoked by uid 500); 11 Nov 2011 10:43:15 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 32123 invoked by uid 99); 11 Nov 2011 10:43:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Nov 2011 10:43:15 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Nov 2011 10:43:13 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id A74B74D0C5 for ; Fri, 11 Nov 2011 10:42:52 +0000 (UTC) Date: Fri, 11 Nov 2011 10:42:52 +0000 (UTC) From: "Jan Lehnardt (Commented) (JIRA)" To: dev@couchdb.apache.org Message-ID: <763495828.20764.1321008172686.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <313991927.12796.1317050188311.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (COUCHDB-1296) _changes style feed for database create/delete MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/COUCHDB-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148414#comment-13148414 ] 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 database. Another desired feature is to put the old DbUpdateNotification stdio API on HTTP under say /_db_updates 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: https://issues.apache.org/jira/browse/COUCHDB-1296 > 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira