You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "Nick Vatamaniuc (JIRA)" <ji...@apache.org> on 2017/04/11 01:35:41 UTC

[jira] [Commented] (COUCHDB-3371) Investigate putting user specified replication filtering function in replication document

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

Nick Vatamaniuc commented on COUCHDB-3371:
------------------------------------------

This was an original idea of Paul Davis, mentioned in the comments of a replication pull request. I just created a ticket to keep track of it.

> Investigate putting user specified replication filtering function in replication document
> -----------------------------------------------------------------------------------------
>
>                 Key: COUCHDB-3371
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-3371
>             Project: CouchDB
>          Issue Type: Improvement
>            Reporter: Nick Vatamaniuc
>
> Investigate letting users specify the filter function in the replication document.
> There are two main reasons for it:
> 1) Because user specified filters live on the source and filter code contents is used to generated replication IDs. In order to even create a replication it is necessary to do a remote network fetch.  This also implies having to handle retries and temporary failures an area of code were this would otherwise not be needed.
> 2) If filtering code is provided in the replication document, replication ID calculation and tracking of changes to replication ID when filter is updated become trivial. Not it ranges from broken to awkwardly complicated



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)