Differences between revisions 3 and 4
Revision 3 as of 2009-09-20 21:44:42
Size: 1264
Editor: localhost
Comment: converted to 1.6 markup
Revision 4 as of 2018-04-13 05:59:28
Size: 0
Editor: JoanTouzet
Comment: Good future-looking idea, but it's never been implemented.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#redirect Document_runner_plugin
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 [[http://mail-archives.apache.org/mod_mbox/incubator-couchdb-user/200806.mbox/%3ce282921e0806130216w3d20dfdfh244ea5b491e12ee5@mail.gmail.com%3e|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)