couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COUCHDB-953) latest=true is ignored in open_revs calls
Date Thu, 18 Nov 2010 08:00:16 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Randall Leeds updated COUCHDB-953:
----------------------------------

    Attachment: 0001-parse-latest-option-for-open_revs-COUCHDB-953.patch

Looks like this might be all it takes since couch_db:open_revs_int/3 seems to handle the option
and get_key_leafs is tested be 063-kt-get-leaves.t.

Good catch.

Is this supposed to allow a source to skip sending some revs over when a consumer is a little
bit behind on the changes feed or a source is updating quickly?

> 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.


Mime
View raw message