couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <>
Subject [jira] Commented: (COUCHDB-892) Method for restarting filtered replication
Date Sat, 25 Sep 2010 12:04:32 GMT


Randall Leeds commented on COUCHDB-892:

I second what Bob said ("I'm surprised..."). I shouldn't be surprised, because I've seen this
code a lot, but oh well.

But I also think a start_seq might turn out to be useful in other situations in the future:
a) an administrator changes the hostname of a box and wants to re-start replication without
starting from the beginning again.
b) fast-forward replication from a source when you trust a third party from which you replicated
the source.
c) scp a .couch file to create a redundant copy and jump-start continuous replication.

> Method for restarting filtered replication
> ------------------------------------------
>                 Key: COUCHDB-892
>                 URL:
>             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.

View raw message