This is a beta release for the 2.11.0 version of the driver.
The main new features in 2.11.0-beta1 support new features in MongoDB 4.4.0. These features include:
- Support for all new
$meta
projections:randVal
,searchScore
,searchHighlights
,geoNearDistance
,geoNearPoint
,recordId
,indexKey
andsortKey
- Support for passing a hint to update commands as well as
findAndModify
update and replace operations - Support for
allowDiskUse
on find operations - Support for
MONGODB-AWS
authentication using Amazon Web Services (AWS) Identity and Access Management (IAM) credentials - Support for stapled OCSP (Online Certificate Status Protocol) (macOS only)
Other new additions and updates in this beta include:
- A new target of .NET Standard 2.0
- Support for Snappy compression on .NET Core on Windows (in addition to existing support on .NET Framework)
- Support for Zstandard compression on Windows on 64-bit platforms
- A new default of enabling certificate revocation checking.
- A new URI option
tlsDisableCertificateRevocationCheck
to disable certificate revocation checking. - An expanded list of retryable write errors via the inclusion of
ExceededTimeLimit
,LockTimeout
andClientDisconnect
- A new GuidRepresentationMode setting to opt-in to the new V3 GuidRepresentation mode
An online version of these release notes is available at:
The full list of JIRA issues that are currently scheduled to be resolved in this release is available at:
The list may change as we approach the release date.
Documentation on the .NET driver can be found at:
https://mongodb.github.io/mongo-csharp-driver/
Because certificate revocation checking is now enabled by default, an
application that is unable to contact the OCSP endpoints and/or CRL
distribution points specified in a server's certificate may experience
connectivity issues (e.g. if the application is behind a firewall with
an outbound whitelist). This is because the driver needs to contact
the OCSP endpoints and/or CRL distribution points specified in the
server’s certificate and if these OCSP endpoints and/or CRL
distribution points are not accessible, then the connection to the
server may fail. In such a scenario, connectivity may be able to be
restored by disabling certificate revocation checking by adding
tlsDisableCertificateRevocationCheck=true
to the application's connection
string.