Docs Menu
Docs Home
/
MongoDB Manual
/
Release Notes
/
7.0

Compatibility Changes in MongoDB 7.0

On this page

  • Deprecations
  • Free Monitoring Decommissioned
  • Queryable Encryption General Availability
  • Backward-Incompatible Features
  • Intra-Node Authentication
  • Time-Series
  • Cluster Configuration
  • Encrypted Multi-Map (EMM)
  • Wildcard Indexes

This page describes changes introduced in MongoDB 7.0 that can affect compatibility with older versions of MongoDB.

MongoDB 7.0 is a Major Release, which means that it is supported for both MongoDB Atlas and on-premises deployments. MongoDB 7.0 includes changes introduced in MongoDB Rapid Releases 6.1, 6.2, and 6.3. This page describes compatibility changes introduced in those Rapid Releases and MongoDB 7.0.

To learn more about the differences between Major and Rapid Releases, see MongoDB Versioning.

For detail on downgrading from MongoDB 7.0, see Downgrade 7.0 to 6.0.

Deprecations

Deprecated
Description
storageDetails
Deprecated in version 7.0.

Free Monitoring Decommissioned

Starting in MongoDB 7.0, free monitoring is decommissioned. The following aren't available:

  • cloud.monitoring.free configuration option

  • --enableFreeMonitoring server parameter

  • db.enableFreeMonitoring() command

  • db.disableFreeMonitoring() command

  • setFreeMonitoring command

Queryable Encryption General Availability

Starting in MongoDB 7.0, Queryable Encryption with equality queries is generally available (GA). Improvements in the GA make it incompatible with the Queryable Encryption Public Preview, which should not be used now that the feature is GA.

Server and Drivers Compatibility Between Public Preview and GA

To use Queryable Encryption with equality queries, MongoDB server must be version 7.0 or later and drivers must be 7.0 compatible. If you are still using the Queryable Encryption Public Preview included with MongoDB 6.x, the server must remain on version 6.x and the drivers must be 6.x compatible. You cannot use MongoDB 6.x compatible drivers with a 7.0 server, or 7.0 compatible drivers with a 6.x server. Attempting to do so results in an error.

To make upgrading easier, MongoDB 7.0 drivers can decrypt data created with MongoDB 6.x drivers. For upgrade options, see the following sections.

Start Fresh (Preferred)

If possible, create new collections rather than migrating those produced with the Queryable Encryption Public Preview in MongoDB 6.x:

  1. Upgrade MongoDB server and drivers to 7.0.

  2. Configure a new encrypted collection with a different name from the previous collection.

  3. Insert new data, or an unencrypted version of the existing data if you have a local copy.

  4. Drop the previous version 6.x collection.

Migration

If you cannot use new data or do not have an unencrypted version of the existing data:

  1. Upgrade MongoDB server and drivers to 7.0

  2. Using a 7.0 compatible driver, query the encrypted collection to decrypt it.

  3. Save the output locally.

  4. Configure a new encrypted collection and ingest the data.

Warning

  • The mongoexport and mongodump operations do not decrypt the collection. You must query the collection from a driver to output the decrypted data.

  • MongoDB 7.0 compatible drivers can't query encrypted fields on data encrypted with MongoDB 6.x compatible drivers. To decrypt data, either query an unencrypted field or query the entire collection.

Backward-Incompatible Features

The following 7.0 features are not compatible with earlier versions of MongoDB. To downgrade from MongoDB 7.0 to an earlier version, you must remove data that uses any of the following features:

  • Collections with encryptedFields with range indexes

  • Compound wildcard indexes require fCV 7.0 or greater. A pre-7.0 mongod does not start if you are using one or more compound wildcard indexes.

  • Config servers that have collections with changeStreamPreAndPostImages enabled

  • Secondary TTL indexes with partial filters on time series collections

  • Time series collections with custom bucketing parameters

Intra-Node Authentication

Starting in MongoDB 7.0, you can configure servers to authenticate X.509 certificates as cluster members identified by attributes or extension values. You can also override this configuration to accept alternate certificates during a rolling upgrade.

To downgrade to MongoDB 6.0, perform the certificate rotation procedure to unset the net.tls.clusterAuthX509 setting and rotate the cluster membership certificates to ones with matching DC, O, and OU attributes.

Once this is complete, you can downgrade the cluster.

Time-Series

  • Remove partial TTL indexes from time series collections.

  • Remove or modify collections using new index parameters. In some cases, you may use collMod to switch to legacy granularity settings, if not you need to drop the collection before downgrading.

Cluster Configuration

Active setClusterParameter parameter operations prevent feature Compatibility Version (fCV) from successful completion.

Encrypted Multi-Map (EMM)

Remove collections that use the encryptedFields collection option before downgrading.

Wildcard Indexes

Compound wildcard indexes require fCV 7.0 or greater. A pre-7.0 mongod does not start if you are using one or more compound wildcard indexes.

OIDC Access Token Authentication Behavior

Starting in MongoDB 7.0, only one audience oidcIdentityProviders field can be specified for OIDC access tokens. audience fields with empty arrays or arrays of multiple strings are invalid.

For details, see oidcIdentityProviders Fields.

Back

7.0

Next

Upgrade 6.0 to 7.0