[
https://issues.apache.org/jira/browse/COUCHDB-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686719#comment-13686719
]
Dave Cottlehuber commented on COUCHDB-1819:
-------------------------------------------
Thanks for logging a ticket on this Stephen. I can see why you might find this
useful but this doesn't feel aligned to CouchDB for me. Functioning replication
(without losing your data during conflict resolution :-) is one of our core
features, and I can't see how this API change would play well with other
Couch-like replication systems if they wish to stay compatible.
Any more details on the use case?
An alternative is to write your own replicator, see
https://groups.google.com/forum/#!msg/nodejs/_v8G6yutMkg/HtgU596_C1QJ and
https://github.com/mikeal/replicate for an example. The replicator is just a
clever HTTP client, so you can do the same thing yourself.
> Support style=main_only as an option on the source feed when replicating
> ------------------------------------------------------------------------
>
> Key: COUCHDB-1819
> URL: https://issues.apache.org/jira/browse/COUCHDB-1819
> Project: CouchDB
> Issue Type: New Feature
> Reporter: Stephen Bartell
> Priority: Minor
>
> The goal is to not propagate conflicts and _deleted_conflicts.
> This of course has the implication of blindly accepting couchdb's default
> conflict resolution algorithm and not giving the user a chance fix conflicts.
--
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
