New Java Driver

[Sean Corfield]

10gen recently rev'd all eight MongoDB drivers and one of the changes was to the default write concern which is now _safe_ (I believe?) which is a stricter requirement than the previous default. I could look it up but I'm being a bit lazy :)

They've done this so the "simple and obvious" use of MongoDB behaves like people from a regular database background might expect: that errors are reported by default.

We normally update to the latest Java driver as a matter of course but this introduces a potentially breaking change for folks who rely on fire'n'forget write concern being the default.

What do folks think about this change - and how should we handle it in CongoMongo?

FWIW, I think this issue needs to be resolved before we move to the new driver:

https://github.com/aboekhoff/congomongo/issues/74

so that people have more control over write concern at an individual operation level.

--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/

"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)

[Sean Corfield]

FYI, there are a whole bunch of new WriteConcern values (I would consider the old ones deprecated) and a new connection class, MongoClient (which is what actually changes the default write concern from None to Normal, as far as I can tell):

http://api.mongodb.org/java/2.10.1/com/mongodb/WriteConcern.html