couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <>
Subject [jira] Commented: (COUCHDB-1024) New replicator implementation
Date Fri, 04 Feb 2011 22:53:30 GMT


Randall Leeds commented on COUCHDB-1024:

I think it is incompatible, but not for the reason I said.

get_rep_endpoint converts from #httpdb{} to {remote, Url, Headers} or {remote, Url, Headers,

But the latest code you just linked adds default headers:

which means we get {remote, Url, [{"Accept", "application/json"}, {"User-Agent", "CouchDB/"
++ couch_server:get_version()}]}

compare to

{remote, Url, []}

Also. If we use default headers there that include a different user agent it means we *guarantee*
we break checkpoints on every version upgrade. No?

> New replicator implementation
> -----------------------------
>                 Key: COUCHDB-1024
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Replication
>            Reporter: Filipe Manana
>            Assignee: Filipe Manana
>             Fix For: 1.2
> As recently posted to the development mailing:
> ( shortened URL )
> There's a new replicator implementation. I won't explain here all the details since it's
already done by that mail sent to the development list.
> @Adam, do you think you can give it a review?
> The full diff is at:
> Would be equally happy if others are able and willing to review and test as well.
> Also take note that some pull replications of databases with attachments created by prior
CouchDB releases (including 1.0.1, but excluding the soon to be released 1.0.2) may hang forever.
This is fixed by applying the patch for COUCHDB-1022 to the source server.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message