Skip to content


Subversion checkout URL

You can clone with
Download ZIP
java driver for mongo
Java Groovy
Pull request Compare This branch is 237 commits behind mongodb:master.
Fetching latest commit...
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

Release Notes

Release notes are available here.

API Documentation:

Javadoc for all major and minor releases is available here.

Support / Feedback

For issues with, questions about, or feedback for the MongoDB Java driver, please look into our support channels. Please do not email any of the Java driver developers directly with issues or questions - you're more likely to get an answer on the mongodb-user list on Google Groups.

At a minimum, please include in your description the exact version of the driver that you are using. If you are having connectivity issues, it's often also useful to paste in the line of code where you construct the MongoClient instance, along with the values of all parameters that you pass to the constructor. You should also check your application logs for any connectivity-related exceptions and post those as well.

Bugs / Feature Requests

Think you’ve found a bug? Want to see a new feature in the Java driver? Please open a case in our issue management tool, JIRA:

Bug reports in JIRA for the driver and the Core Server (i.e. SERVER) project are public.

If you’ve identified a security vulnerability in a driver or any other MongoDB project, please report it according to the instructions here.


Major increments (such as 2.x -> 3.x) will occur when break changes are being made to the public API. All methods and classes removed in a major release will have been deprecated in a prior release of the previous major release branch, and/or otherwise called out in the release notes.

Minor 3.x increments (such as 3.1, 3.2, etc) will occur when non-trivial new functionality is added or significant enhancements or bug fixes occur that may have behavioral changes that may affect some edge cases (such as dependence on behavior resulting from a bug). An example of an enhancement is a method or class added to support new functionality added to the MongoDB server. Minor releases will almost always be binary compatible with prior minor releases from the same major release branch, exept as noted below.

Patch 3.x.y increments (such as 3.0.0 -> 3.0.1, 3.1.1 -> 3.1.2, etc) will occur for bug fixes only and will always be binary compitible with prior patch releases of the same minor release branch.


APIs marked with the @Beta annotation at the class or method level are subject to change. They can be modified in any way, or even removed, at any time. If your code is a library itself (i.e. it is used on the CLASSPATH of users outside your own control), you should not use beta APIs, unless you repackage them (e.g. by using shading, etc).


APIs marked with the @Deprecated annotation at the class or method level will remain supported until the next major release but it is recommended to stop using them.


All code inside the com.mongodb.internal.* packages is considered private API and should not be relied upon at all. It can change at any time.


Binaries and dependency information for Maven, Gradle, Ivy and others can be found at

Example for Maven:


For an all-in-one jar (which embeds the core driver and bson):


Snapshot builds are also published regulary via Sonatype.

Example for Maven:


For binaries containing the asynchronous API, see the driver-async README.


To build the driver:

$ git clone
$ cd mongo-java-driver
$ ./gradlew check

Build status:

Build Status | Build Status



Additional contributors can be found here.


YourKit is supporting this open source project with its YourKit Java Profiler.

JetBrains is supporting this open source project with:

Intellij IDEA

Something went wrong with that request. Please try again.