You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Jan Lehnardt (JIRA)" <ji...@apache.org> on 2011/04/17 15:00:05 UTC
[jira] [Resolved] (COUCHDB-892) Method for restarting filtered
replication
[ https://issues.apache.org/jira/browse/COUCHDB-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Lehnardt resolved COUCHDB-892.
----------------------------------
Resolution: Fixed
This has been fixed a while ago. Closing.
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira