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



Riak Map/Reduce Improvements Explained

Riak 0.14.0 included a couple of very exciting improvements for Map/Reduce. In a recent post, Basho guys are spending again some time to explain them:

If the application can store meaningful data in the keys, then key filtering can query just the keys and load only the objects whose keys pass the filter to be processed by the MapReduce job. […] Key filtering will support boolean operators (and, or, not), url decoding, string tokenizing, regular expressions, and various string to numeric conversions.

Similar to Kevin Smith’s presentation on Riak map/reduce improvements, this post covers also the Map/Reduce query planner and the optimized JavaScript VM pools.

Original title and link: Riak Map/Reduce Improvements Explained (NoSQL databases © myNoSQL)