MongoDB v2.11.0-beta1 Release Notes
Release Date: 2020-04-10 // almost 4 years ago-
π .NET Driver Version 2.11.0-beta1 Release Notes
π 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
and
sortKey
- π 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
- 0οΈβ£ 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:
http://mongodb.github.io/mongo-csharp-driver/
β¬οΈ Upgrading
Backwards compatibility with driver version 2.7.0β2.10.x
0οΈβ£ 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. - π Support for all new