The ClojureWerkz Blog

News and updates about ClojureWerkz projects

Monger 1.4.0 Is Released

TL;DR

Monger is an idiomatic Clojure MongoDB driver for a more civilized age. It has batteries included, offers powerful expressive query DSL, strives to support every MongoDB 2.0+ feature and has sane defaults. It also has solid documentation.

1.4.0 is a minor almost (but not completely) backwards-compatible release that upgrades MongoDB Java driver and Cheshire and adapts to their public API changes.

Changes in 1.4.0

MongoDB Java Driver Update

MongoDB Java driver dependency has been updated to 2.10.0. If your code depends on the exact class com.mongodb.Mongo, it should be updated to use com.mongodb.MongoClient (or not depend on specific class names at all).

In addition, MongoOptions and MongoURI in the new driver have changed to MongoClientOptions and MongoClientURI, respectively.

Cheshire 0.5.0

monger.json and monger.joda-time will use Cheshire if it is available and now requires Cheshire version 5.0. clojure.data.json is no longer a hard dependency (but 0.1.x versions are still supported if available).

Recently released clojure.data.json version 0.2.0 is now supported. We strongly recommend all users to use Cheshire when possible.

Cheshire 5.0 change log is available on GitHub.

ClojureWerkz Support 0.9.0

ClojureWerkz Support library is upgraded to 0.9.

Change Log

We recommend all users to upgrade to 1.4.0 as soon as possible.

Monger change log is available on GitHub.

Monger is a ClojureWerkz Project

Monger is part of the group of libraries known as ClojureWerkz, together with

  • Welle, a Riak client with batteries included
  • Elastisch, a minimalistic Clojure client for ElasticSearch
  • Neocons, a client for the Neo4J REST API
  • Langohr, a Clojure client for RabbitMQ that embraces the AMQP 0.9.1 model
  • Quartzite, a powerful scheduling library

and several others. If you like Monger, you may also like our other projects.

Let us know what you think on Twitter or on the Clojure mailing list.

@michaelklishin on behalf of the ClojureWerkz Team