couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-494) Add include_seqs=true option to _all_dbs to allow efficient bootstrapping of external indexes.
Date Fri, 25 Mar 2011 19:06:05 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011362#comment-13011362
] 

Adam Kocoloski commented on COUCHDB-494:
----------------------------------------

Hi, it hasn't been resolved.  It's a bit problematic, though.  The current implementation
of _all_dbs has the nice property that it doesn't actually open any of the databases when
it generates the response.  If we added the sequence numbers I think we'd also need to add
pagination to avoid an attempt to open 1000s of databases in rapid succession.  I also think
this needs to be opt-in to avoid making a breaking change to the API.

> Add include_seqs=true option to _all_dbs to allow efficient bootstrapping of external
indexes.
> ----------------------------------------------------------------------------------------------
>
>                 Key: COUCHDB-494
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-494
>             Project: CouchDB
>          Issue Type: New Feature
>          Components: Database Core
>            Reporter: Robert Newson
>
> External indexers need an efficient way to detect changes across all databases when they
boot up. The _all_dbs endpoint only lists the names. We propose adding include_seqs=true which
would return this style output instead;
> [ {"name":"db1","update_seq",5000}, {"name":"db2","update_seq",2500} ]
> this would allow an external indexer to skip any database that has not changed.
> As external indexers often store their configuration changes inside design documents,
it might also be helpful if the update_seq of the latest change to any design document was
also included. This will allow external indexers to skip even databases with changes as long
as those changes are not to design documents;
> [ {"name":"db1","update_seq",5000, "ddoc_update_seq":23}, {"name":"db2","update_seq",2500,
"ddoc_update_seq":2500} ]

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message