ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

A MongoDB Map/Reduce Job Explained

A real-world MongoDB map/reduce example used by the private group mailing lists tool Fiesta explained in detail. The only part I don’t agree with is emphasized below:

Map/Reduce is a great way to do aggregations and ETL-type operations with MongoDB.

Probably nitpicking, but MongoDB’s MapReduce—actually this applies to most NoSQL databases MapReduce implementations: CouchDB, Riak, etc.—can do only the transform part and very less so load[1] and no extract.


  1. One could argue that MongoDB’s out option can be seen as equivalent to the load phase, but we can agree that having the results replacing or merged in a collection is just a use case  

Original title and link: A MongoDB Map/Reduce Job Explained (NoSQL database©myNoSQL)

via: http://blog.fiesta.cc/post/10980328832/walkthrough-a-mongodb-map-reduce-job