[
https://issues.apache.org/jira/browse/COUCHDB-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990794#comment-12990794
]
Filipe Manana commented on COUCHDB-1024:
----------------------------------------
First of all, thanks everyone for the reviews and +1 votes. This is really
important and a major change to add.
Randall, I don't think there is any incompatibility. The new replicator still
uses tuples like {remote, Url, []} for calculating the replication IDs. Look at:
https://github.com/fdmanana/couchdb/blob/trunk_new_replicator/src/couchdb/couch_replicator_utils.erl#L122
and
https://github.com/fdmanana/couchdb/blob/trunk_new_replicator/src/couchdb/couch_replicator_utils.erl#L168
get_rep_endoint converts from #httpdb{} to {remote, Url, OAuthList}
> New replicator implementation
> -----------------------------
>
> Key: COUCHDB-1024
> URL: https://issues.apache.org/jira/browse/COUCHDB-1024
> Project: CouchDB
> Issue Type: Improvement
> Components: Replication
> Reporter: Filipe Manana
> Assignee: Filipe Manana
> Fix For: 1.2
>
>
> As recently posted to the development mailing:
> http://mail-archives.apache.org/mod_mbox/couchdb-dev/201101.mbox/%[email protected]%3E
> ( shortened URL http://s.apache.org/KsY )
> 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:
> https://github.com/fdmanana/couchdb/compare/trunk_new_replicator
> 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: http://www.atlassian.com/software/jira
