News for hackers. Stuff that matters.
Re:MongoDB 1.8 (stable) released by rch on Wednesday March 16, 2011 @04:01PM (#2333614)
This is exciting: db.users.mapReduce(map, reduce, {out: { inline : 1}});

This is Not exciting:

"Note that this option is possible only when the result set fits within the 16MB limit of a single document."

Re:MongoDB 1.8 (stable) released by rit on Wednesday March 16, 2011 @04:34PM (#2333768)
I did a writeup, for what it's worth, on the new MapReduce output options:

http://blog.evilmonkeylabs.com/2011/01/27/MongoDB-1_8-MapRed...

(Disclaimer, I work for 10gen / MongoDB)

Re:MongoDB 1.8 (stable) released by rch on Wednesday March 16, 2011 @04:47PM (#2333832)
Very nice - worth the reading. I'm particularly interested in seeing how you've implemented 'merge' and 'reduce' output.

You guys do seem to be headed in the right direction technically... I just can't bring myself to say "mongo" out loud.

Re:MongoDB 1.8 (stable) released by dacort on Wednesday March 16, 2011 @04:06PM (#2333640)
Not really a big deal to just output to a new collection and query that.
Re:MongoDB 1.8 (stable) released by rch on Wednesday March 16, 2011 @04:19PM (#2333703)
Sure - I'm just pointing out something that could be a big deal (streaming results through an ordered structure in memory, that may or may not be backed by a lazy disk store) is actually not a big deal, due to a current implementation constraint.

But you're right too, of course.

Re:MongoDB 1.8 (stable) released by dacort on Wednesday March 16, 2011 @04:35PM (#2333776)
Yea, makes sense. That limit almost seems to fall along the lines of "Nobody should need more than 16MB for inline map/reduce results." ;)
Re:MongoDB 1.8 (stable) released by rch on Wednesday March 16, 2011 @04:48PM (#2333840)
cheers to that.