[
https://issues.apache.org/jira/browse/COUCHDB-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933444#action_12933444
]
Adam Kocoloski commented on COUCHDB-953:
----------------------------------------
Yes, that's the basic idea. If a source document is updated while the target
is analyzing revisions the source should be free to replace the requested
missing revisions with the leaf revisions of the edit branch on which it lives.
I agree that the only bug is in the HTTP layer and that your patch addresses
it. But it inadvertently includes a few other things - can you clean it up?
> latest=true is ignored in open_revs calls
> -----------------------------------------
>
> Key: COUCHDB-953
> URL: https://issues.apache.org/jira/browse/COUCHDB-953
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Reporter: Adam Kocoloski
> Priority: Minor
> Attachments: 0001-parse-latest-option-for-open_revs-COUCHDB-953.patch
>
>
> The replicator requests documents from a remote source with
> open_revs=[<revlist>]&latest=true, but latest=true is ignored. The option is
> supposed to tell the source to send the leafs of an edit branch containing a
> requested revision, i.e. if the document has been updated since the revlist
> was calculated, the source is free to send the new one.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
