Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Mon, 1 Jul 2013 11:52:20 +0000 (UTC)
From: "Alexander Shorin (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12532469.1322052617263.191231.1372679540537@arcas>
In-Reply-To: <JIRA.12532469.1322052617263@arcas>
References: <JIRA.12532469.1322052617263@arcas>
Subject: [jira] [Commented] (COUCHDB-1345) Bulk edit document on the server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alexander Shorin commented on COUCHDB-1345:
-------------------------------------------

This idea is implemented in [couch_normalizer|https://github.com/datahogs/couch_normalizer] project which acts as CouchDB plugin.
                
> Bulk edit document on the server
> --------------------------------
>
>                 Key: COUCHDB-1345
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1345
>             Project: CouchDB
>          Issue Type: Wish
>            Reporter: Jan Lehnardt
>
> [moved here from the wiki]
> A Document Runner would provide functionality to run a transform function across all documents in the database. This way you could do maintenance and migrations, with incurring a bunch of http overhead.
> The idea was originally floated on the couchdb-user mailing list.
> Requirements
> Ability to specify a job in a view-server like context (Javascript other language function) and have it run across all docs (like a view is), but with the additional ability to write back to the document (through the http api, so we don't have to add a socket-based update interface).
> Caveat:
> We may not be able to guarantee that runner functions see each document only once, so functions need to be aware only to modify documents that require modification.
> Uses
> Changing the format of a timestamp across all docs
> Removing sensitive fields before replicating to another jurisdiction
> (View runner... slightly different) Materializing the results of group=true reduce queries into a dataset for further map/reduce processing (a common pattern in Hadoop)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira