MongoDB 1.8 (stable) released

#1

Post by luigi » Wed, Mar 16, 2011, 7:34 PM UTC

MongoDB 1.8 (stable) released
blog.mongodb.org

Re: MongoDB 1.8 (stable) released

#2

Post by rbranson » Wed, Mar 16, 2011, 7:45 PM UTC

Starting to get excited once again about MongoDB. I was kind of down about it after having some issues with real world implementations. Considering journaling is something I would never have thought would have made it in, I wonder if they will come around on the memory mapped I/O like everyone else eventually does.

EDIT: Also... does the group commit mean that ALL write transactions will be un-acknowledged to the client until the group commit finishes?

Re: MongoDB 1.8 (stable) released

#3

Post by suhail » Wed, Mar 16, 2011, 7:50 PM UTC

yay "Tab completion in the shell" and "B-tree index self-compaction" are great. So is --journal.

Re: MongoDB 1.8 (stable) released

#4

Post by [deleted] » Wed, Mar 16, 2011, 7:54 PM UTC

[deleted]

Re: MongoDB 1.8 (stable) released

#5

Post by rb2k_ » Wed, Mar 16, 2011, 7:57 PM UTC

suhail wrote: post #3

yay "Tab completion in the shell" and "B-tree index self-compaction" are great. So is --journal.

Do you happen to know details about the B-tree index self-compaction? I can't seem to find it in their changelog on jira ( http://jira.mongodb.org/browse/SERVER?report=com.atlassian.j... )

Re: MongoDB 1.8 (stable) released

#6

Post by rb2k_ » Wed, Mar 16, 2011, 7:59 PM UTC

Can't wait until they start implementing filtered indexes ( http://jira.mongodb.org/browse/SERVER-785 ). Sparse indexes are a step in the right direction, but filtered ones would be just a bit cooler :)

"New map/reduce options for incremental updates" would also be really cool if they had a way to do something like couchDBs incremental views. This would require keeping track of changes or a "trigger" functionality that runs the m/r task after every x inserts

Re: MongoDB 1.8 (stable) released

#7

Post by rch » Wed, Mar 16, 2011, 8:01 PM UTC

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

#8

Post by baltcode » Wed, Mar 16, 2011, 8:03 PM UTC

[deleted] wrote: post #4

[deleted]

Even numbers after the period are good, odd are bad. Large numbers after second period are bad.

Re: MongoDB 1.8 (stable) released

#9

Post by davidw » Wed, Mar 16, 2011, 8:04 PM UTC

MongoDB is not something I have a good handle on yet. What's its sweet spot? Where should I consider using it instead of Postgres?

Re: MongoDB 1.8 (stable) released

#10

Post by dacort » Wed, Mar 16, 2011, 8:06 PM UTC

rch wrote: post #7

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."

Not really a big deal to just output to a new collection and query that.