[SERVER-17354] Automatic incremental map-reduce Created: 23/Feb/15  Updated: 06/Dec/22  Resolved: 04/Feb/22

Status: Closed
Project: Core Server
Component/s: MapReduce
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Kristijan Trajkovski Assignee: Backlog - Query Execution
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-508 Update map reduce collections Closed
Assigned Teams:
Query Execution
Participants:

 Description   

Hi,
I've been testing out couchdb, and came across the concept of views.
Views in couchdb are keeping a pre-calculated map-reduce on all data in one database(collection), and they are updated automatically on every change on the original data set.
Knowing that mongodb supports mapreduce, i think it would be a good idea to be able to set up mapreduce that would output to another collection while keeping the mapreduced data synchronized based on inserts, updates, and deletions of the documents in the original collection.

Often there are times where mapreduce is necessary to be used, and keeping the data set synchronized without the hassle or delay of the current incremental mapreduce method will make lives easier.

For details about the implementation in couchdb, read the following articles:
http://horicky.blogspot.com/2008/10/couchdb-implementation.html (sections Views Indexes and Incremental View Update)
http://damienkatz.net/2008/02/incremental_map.html



 Comments   
Comment by Esha Bhargava [ 04/Feb/22 ]

Closing these tickets as part of the deprecation of mapReduce.

Generated at Thu Feb 08 03:44:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.