[
https://issues.apache.org/jira/browse/COUCHDB-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488911#comment-13488911
]
Jens Alfke commented on COUCHDB-1584:
-------------------------------------
This may actually not be sufficient to let the replicator fetch revisions in
bulk. The problem is that _all_docs takes an array of docids, but not revids —
so the caller has no control over which revision of a document to get; they'll
always get the winning one. So
(a) If a document is in conflict, the replicator will still have to use
single-revision GETs to fetch the non-winning revision(s).
(b) There can be race conditions where a document is updated after the _changes
feed is sent, so the _all_docs request will return that new revision, not the
one the replicator knows about.
I don't think either of these cases will be all that common; it just means the
replicator will have to be a bit careful to check the revids in the response
from _all_docs, and possibly fetch some revisions one-by-one if it didn't get
the right ones.
> Allow passing of open_doc parameters to _all_docs
> -------------------------------------------------
>
> Key: COUCHDB-1584
> URL: https://issues.apache.org/jira/browse/COUCHDB-1584
> Project: CouchDB
> Issue Type: New Feature
> Affects Versions: 1.2
> Reporter: Jan Lehnardt
> Priority: Minor
>
> GET /_all_docs should take the same arguments as GET /db/doc
> /_all_docs?revisions=true
> /_all_docs?revs_info=true
> See http://wiki.apache.org/couchdb/HTTP_Document_API#GET for details
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
