[
https://issues.apache.org/jira/browse/COUCHDB-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914801#action_12914801
]
Filipe Manana commented on COUCHDB-892:
---------------------------------------
Adding the start_seq field to a replication object is the simplest way of doing
it.
Otherwise the replicator must use the entire string of the filter function
(which resides in a design doc of the source DB) as part of the input to the
MD5 function used to calculate the replication ID.
Please, give your opinions.
> Method for restarting filtered replication
> ------------------------------------------
>
> Key: COUCHDB-892
> URL: https://issues.apache.org/jira/browse/COUCHDB-892
> Project: CouchDB
> Issue Type: New Feature
> Components: Replication
> Reporter: Marco Monteiro
> Assignee: Filipe Manana
> Priority: Minor
>
> I'm using filtered replication to maitain a database that has a subset of the
> documents of some other database.
> The problem I have is when I change the filter. If the filter allows for more
> documents to be replicated, those that
> were created before the last replication are not replicated. So, I have to
> remove the database and recreate it.
> I see two solutions that can be implemented to help in this situation. The
> first one is for the filtered replication
> to restart whenever the filter changes (maybe also adding an argument to
> replicate to tell that" we want this to happen).
> Another solution is to add an argument to replicate ("start_seq", as sugested
> by fdmanana on IRC) that would be the
> source database ""local_seq that we want the replication to start from. This
> an be set to 1 to restart from first change.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
