What's New
On this page
Learn what's new in:
What's New in 5.2
New features of the 5.2 driver release include:
A forward-slash (
/
) character between the host names and client options in a connection URI is optional. The driver parses the following connection URI examples in the same way:// Connection URI with delimiting forward-slash String uri = "mongodb://example.com/?w=majority"; // Connection URI without delimiting forward-slash String uri = "mongodb://example.com?w=majority";
Adds the
SearchIndexType
class, which you can pass when constructing aSearchIndexModel
instance. This change allows you to specify the index type when creating an Atlas Search or Vector Search index. To learn more, see Atlas Search and Vector Search Indexes in the Indexes guide.Delegates the implementation of the algorithms that implement the
SCRAM-SHA-1
andSCRAM-SHA-256
authentication mechanisms to the configured JCA provider. This change means that your application can use a configured FIPS-compliant JCA provider to provide a higher level of security.Revises the mongodb-crypt dependency versioning to match the versioning for the JVM drivers. Future versions of
mongodb-crypt
will be released alongside the driver and will share the same version number. You must upgrade yourmongodb-crypt
dependency to v5.2.0 when upgrading your driver for this release. To learn more, see the In-Use Encryption guide.Performance improvements due to implementation of native cryptography on all supported platforms. The following list describes the actions needed to implement this improvement depending on your operating system:
Windows: Upgrade your
mongodb-crypt
version to v5.2.0.Mac: Upgrade your
mongodb-crypt
version to v5.2.0.Linux: Install
libmongocrypt.so
directly on the file system, instead of using the file that is bundled within themongodb-crypt
JAR file. You can find Linux instructions to installlibmongocrypt
in the Server manual. If you use a package manager to installlibmongocrypt
, Java Native Access (JNA) will find it there without further configuration. Alternatively, you can specify the search path by setting theLD_LIBRARY_PATH
environment variable to the file path of thelibmongocrypt
package.We recommend direct installation because the bundled shared library does not link with OpenSSL due to the potential for OpenSSL binary incompatibilities.
The shared library loading is handled by JNA. You can view the rules for library loading search path order in the NativeLibrary class documentation.
Fixes an issue that caused the
InsertOneResult.getInsertedId()
andInsertManyResult.getInsertedIds()
methods to return incorrect document IDs in some situations. This change is backported to Java driver v5.1.4 and v4.11.4.When a sharded cluster operation is unsuccessful, the driver avoids selecting the same
mongos
server for operation retry attempts if othermongos
servers are available.Adds reachability metadata needed when your application uses GraalVM Native Image. This metadata replaces the need for collecting reachability metadata when using the driver libraries. To learn more, see Reachability Metadata in the GraalVM documentation.
This change does not add the
libjnidispatch
andlibmongocrypt
resource entries, because adding entries for all supported platforms (targets) significantly affects the size of native executables built using GraalVM Native Image. View this sample resource-config.json file in the driver GitHub repository to see how to specify these entries explicitly if your application depends on theorg.mongodb:mongodb-crypt
library.Enables exact vector search by extending the
VectorSearchOptions
API to introduce the following specific option subtypes:ExactVectorSearchOptions
: Use this options type to enable precise matching, ensuring that results are the closest vectors to a given query vector.ApproximateVectorSearchOptions
: Use this options type to enable searches that might not return the exact closest vectors. You can pass anumCandidates
parameter when instantiating this type to specify the number of nearest neighbors to consider.
To learn more about using the Atlas Vector Search feature, see Atlas Vector Search in the Aggregates Builders guide.
What's New in 5.1.3
The 5.1.3 driver patch release includes the following changes:
Fixes an issue that could cause assertion errors when using
Cursor
types.
What's New in 5.1.2
The 5.1.2 driver patch release includes the following changes:
Fixes an issue that prevents the driver from encoding and decoding concrete classes that extend generic base classes, in cases that you specify the base class as the generic type of the
MongoCollection
instance.Fixes an issue related to how domain names are validated when you use SOCKS5 proxy functionality, allowing you to use domain names with more than six characters in the top-level domain.
What's New in 5.1.1
The 5.1.1 driver patch release includes the following changes:
When using the
MONGODB-OIDC
authentication mechanism, you must not include comma characters in theauthMechanismProperties
connection string value. To learn more about this behavior, see the MONGODB-OIDC section of the Enterprise Authentication guide.Optimizes GridFS throughput by removing redundant byte array cloning. The
GridFSDownloadStream
andGridFSUploadStream
types use theBsonDocument
type instead ofDocument
.
What's New in 5.1
Warning
Deprecations in this release
To avoid breaking changes in future major releases of the driver, replace any application code that depends on deprecated program elements.
This section includes the following information:
Deprecations in 5.1
Support for MongoDB Server v3.6 is deprecated and will be removed in the next driver version release. To learn how to upgrade your MongoDB Server deployment, see Release Notes in the MongoDB Server manual.
Improvements in 5.1
Internal testing of GraalVM native image technology. These tests involve building native applications by using the GraalVM native-image tool.
Enhanced support for the MONGODB-OIDC authentication mechanism. For more information about OIDC, see the MONGODB-OIDC section of the Enterprise Authentication Mechanisms guide.
New Features in 5.1
Introduces the
serverMonitoringMode
connection URI option. For more information about this option, see the Connection Options guide.
What's New in 5.0
Warning
Breaking changes in this release
This driver version introduces breaking changes. For a list of these changes, see the Version 5.0 Breaking Changes section in the Upgrade guide.
Warning
Deprecations in this release
To avoid breaking changes in future major releases of the driver, replace any application code that depends on deprecated program elements.
This section includes the following information:
Deprecations in 5.0
The
org.mongodb.scala.Observable.completeWithUnit()
method is deprecated. This method is not useful anymore because the driver now exposesorg.mongodb.scala.Observable[Unit]
instead oforg.mongodb.scala.Observable[Void]
. This relates to a breaking change about Observables in this release.
Behavioral changes in 5.0
The
getElapsedTime()
method oncom.mongodb.event.ConnectionReadyEvent
includes the time taken to deliver theConnectionCreatedEvent
. That is, the time returned includes the duration of thecom.mongodb.event.ConnectionPoolListener.connectionCreated()
method.The
getElapsedTime()
methods oncom.mongodb.event.ConnectionCheckedOutFailedEvent
andcom.mongodb.event.ConnectionCheckedOutEvent
include the time taken to deliver thecom.mongodb.event.ConnectionCheckOutStartedEvent
. That is, the time returned includes the duration of thecom.mongodb.eventConnectionPoolListener.connectionCheckOutStarted()
method.
New features in 5.0
The 5.0 driver release introduces the following features:
Adds support for the
authorizedCollection
option of thelistCollections
command. This was done by changing thecom.mongodb.client.MongoDatabase.listCollectionNames()
methods. The return type is nowcom.mongodb.client.ListCollectionNamesIterable
, while previously it was aMongoIterable<String>
. This change allows the return value to be configured using theListCollectionNamesIterable.authorizedCollections()
method and specifying theauthorizedCollections
option. Equivalent changes were made to following classes and interfaces:com.mongodb.reactivestreams.client.MongoDatabase
org.mongodb.scala.MongoDatabase
com.mongodb.kotlin.client.MongoDatabase
com.mongodb.kotlin.client.coroutine.MongoDatabase
These changes introduce a binary breaking change to the listCollectionsNames() method. For more information about the
MongoDatabase.listCollectionNames()
method and theauthorizedCollections
option, see the listCollections Server manual page or Get a List of Collections.
Note
The v5.0.2 patch release fixed an issue related to how domain names are validated when you use SOCKS5 proxy functionality, allowing you to use domain names with more than six characters in the top-level domain.
What's New in 4.11
This section includes the following information:
Deprecations in 4.11
Warning
Deprecations in this release
To avoid breaking changes in future major releases of the driver, replace any application code that depends on deprecated methods and types.
The 4.11 driver release deprecates the following items:
The
getStats()
andisCapped()
instance methods of theDBCollection
class are deprecated. The corresponding server commands are deprecated in MongoDB v6.2 and later. Use the$collStats
aggregation pipeline stage to retrieve the information provided by these methods instead. You can run the aggregation as shown in the following code example:Cursor cursor = collection.aggregate(Arrays.asList( new BasicDBObject("$collStats", new BasicDBObject("storageStats", new BasicDBObject()))), AggregationOptions.builder().build() ); To determine whether a collection is a capped collection, access the value of the
storageStats.capped
field returned byCursor
instance in the preceding example aggregation.To learn more about the
$collStats
aggregation operator, see the $collStats (aggregation) Server manual entry.The following network address-related methods are deprecated and will be removed in v5.0:
The ServerAddress methods
getSocketAddress()
andgetSocketAddresses()
.Instead of
getSocketAddress()
, use thegetByName()
instance method ofjava.net.InetAddress
.Instead of
getSocketAddresses()
, use thegetAllByName()
instance method ofjava.net.InetAddress
.The UnixServerAddress method
getUnixSocketAddress()
.Instead of
getUnixSocketAddress()
, construct an instance ofjnr.unixsocket.UnixSocketAddress
. Pass the full path of the UNIX socket file to the constructor. By default, MongoDB creates a UNIX socket file located at"/tmp/mongodb-27017.sock"
. To learn more about theUnixSocketAddress
, see the UnixSocketAddress API documentation.
The following methods and types related to the StreamFactory interface are deprecated and scheduled for removal in v5.0:
streamFactoryFactory()
method fromMongoClientSettings.Builder
getStreamFactoryFactory()
method fromMongoClientSettings
NettyStreamFactoryFactory
classNettyStreamFactory
classAsynchronousSocketChannelStreamFactory
classAsynchronousSocketChannelStreamFactoryFactory
classBufferProvider
classSocketStreamFactory
classStream
classStreamFactory
classStreamFactoryFactory
classTlsChannelStreamFactoryFactory
class
If you configure Netty by using
MongoClientSettings.Builder.streamFactoryFactory()
, your code might resemble the following:import com.mongodb.connection.netty.NettyStreamFactoryFactory; // ... MongoClientSettings settings = MongoClientSettings.builder() .streamFactoryFactory(NettyStreamFactoryFactory.builder().build()) .build(); Replace this code with the TransportSettings.nettyBuilder() as shown in the following example:
import com.mongodb.connection.TransportSettings; // ... MongoClientSettings settings = MongoClientSettings.builder() .transportSettings(TransportSettings.nettyBuilder().build()) .build();
New Features in 4.11
New features of the 4.11 driver release include:
Support for connecting to MongoDB by using a SOCKS5 proxy. To learn more see Connect to MongoDB by Using a SOCKS5 Proxy.
Note
The v4.11.3 patch release fixed an issue related to how domain names are validated when you use SOCKS5 proxy functionality, allowing you to use domain names with more than six characters in the top-level domain.
Added the
getSplitEvent()
method to theChangeStreamDocument
class to identify fragments of a change stream event that exceeds 16MB. You must use the aggregation stage$changeStreamSplitLargeEvent
in your change stream to handle events that exceed 16MB. To learn more, see Split Large Change Stream Events.Added an aggregation stage builder for
$vectorSearch
. To learn more, see Atlas Vector Search.Added Atlas Search index management helpers. To learn more, see Atlas Search Indexes.
Updated Snappy and Zstd compression library dependency versions. To learn more about the current dependency versions, see Network Compression.
Added
getElapsedTime()
methods to the following classes to monitor the duration of connection pool events:Support for Java 21 virtual threads and structured concurrency. The driver internals were updated to avoid unnecessary pinning of virtual threads and to preserve interrupted status of a thread, as the latter matters for structured concurrency where it is used for cancellation.
To learn more about virtual threads, see the Virtual Threads JDK enhancement proposal. To learn more about structured concurrency, see the Structured Concurrency JDK enhancement proposal.
Updated API documentation for the following types:
What's New in 4.10
New features of the 4.10 driver release include:
Implementation of the
Accumulators.percentile()
andAccumulators.median()
methods for statistical aggregations.Interfaces in the
com.mongodb.client.model.search
package are now marked as@Sealed
instead of@Evolving
. Sealed interfaces must not be extended or implemented by consumers of the library.Resolved an issue where the driver emitted duplicate log messages for retry operations. The driver now correctly emits one log message for each retry operation.
The
org.bson.codecs.Parameterizable
interface is deprecated. Instead of implementing this interface on a customCodec
type, override theCodecProvider.get()
method on the codec'sCodecProvider
if the codec is intended for a parameterized type.Support for custom DNS resolvers.
Support for Queryable Encryption (QE). To learn more about the requirements for using the QE feature, see the Queryable Encryption Driver Compatibility Table.