couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dirkjan Ochtman (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-686) Improve ordering of replication
Date Wed, 10 Mar 2010 09:55:27 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843502#action_12843502
] 

Dirkjan Ochtman commented on COUCHDB-686:
-----------------------------------------

Hmm, so I read somewhere that continuous replication just uses the changes feed off of the
source db. If that's true, maybe we can restrict this further to continuous replication only,
and have it use the changes feed with include_docs=true? That should make it even easier,
and faster to do this.

> Improve ordering of replication
> -------------------------------
>
>                 Key: COUCHDB-686
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-686
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Replication
>    Affects Versions: 0.10.1
>            Reporter: Dirkjan Ochtman
>            Priority: Minor
>             Fix For: 0.12
>
>
> Currently, (continuous) replication almost preserves the ordering of the updates. It
would be nice if this could be fixed so that the order of outgoing updates fully corresponds
to the order inside the source database. While this may fall down in some clustering situations,
it's a great guarantee to provide in many smaller situations involving an ordered stream of
documents/updates.

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