- Upgrade Considerations
Upgrading from 3.8.x
Numerous classes and methods have been deprecated in the 3.9 release in preparation for a major 4.0 release, in which all deprecated API elements except those documented as “not currently scheduled for removal” will be removed. Currently the only API elements not scheduled for removal are:
To prepare for the 4.0 release, please compile with deprecation warnings enabled and replace all usage of deprecated API elements with their recommended replacements.
Also, note that the 3.10 release (which will include support for MongoDB 4.2) will be the last release that is compatible with Java 6 or Java 7. The 4.0 Java driver will require a minimum of Java 8. The 3.10 release will also be the last non-patch release in the 3.x line. In particular, support for MongoDB 4.4 will only be made available via a 4.x driver release.
The 3.9 release is binary and source compatible with the 3.8 release, except for methods that have been added to interfaces that have been marked as unstable, and changes to classes or interfaces that have been marked as internal or annotated as Beta.
Upgrading from 2.x
See the Upgrade guide in the 3.0 driver reference documentation for breaking changes in 3.0.
The minimum JVM is Java 6. However, specific features require more recent versions:
- Atlas M0 (Free Tier) support requires Java 8 or greater due to its reliance on TLS Server Name Indication (SNI).
- SSL support requires Java 7 or greater in order to perform host name verification, which is enabled by default. See SSL for details on how to disable host name verification.
- The asynchronous API requires Java 7, as by default it relies on
AsynchronousSocketChannelfor its implementation. See Async for details on configuring the driver to use Netty instead.
The following table specifies the compatibility of the MongoDB Java driver for use with a specific version of MongoDB.
|Java Driver Version||MongoDB 2.6||MongoDB 3.0||MongoDB 3.2||MongoDB 3.4||MongoDB 3.6||MongoDB 4.0|