On this page
MongoDB 5.2 is a rapid release and is only supported for MongoDB Atlas. MongoDB 5.2 is not supported for use on-premises. For more information, see MongoDB Versioning.
MongoDB 5.2 Released January 19, 2022
- SERVER-63145 Query $densify produces incorrect results with optimizations enabled
- SERVER-62981 Make SBE multi-planner's trial period termination condition independent of collection size
- SERVER-62277 Performance regression from dbstats due to occupied disk space calculation
- SERVER-62065 Upgrade path from 3.6 to 4.0 can leave chunk entries without history on the shards
- SERVER-59754 Incorrect logging of queryHash/planCacheKey for operations that share the same $lookup shape
- All JIRA issues closed in 5.2.1
- 5.2.1 Changelog
MongoDB 5.2 introduces the following aggregation operators:
Returns the bottom element within a group according to the specified sort order.
Returns an aggregation of the bottom
Returns an aggregation of the first
Returns a specified number of elements from the beginning of an array. Distinct from the
Returns an aggregation of the last
Returns a specified number of elements from the end of an array. Distinct from the
Last observation carried forward. Sets values for
Returns an aggregation of the
Returns an aggregation of the
Returns the top element within a group according to the specified sort order. Distinct from the command
Returns an aggregation of the top
Sorts an array based on its elements.
$convert Supports Timestamp Conversion to Date
Starting in MongoDB 5.2 and 5.0.6,
metrics are more precise: internal
processing does not inflate the counters.
Slot-Based Query Execution Engine Can Execute
- The first stage in the pipeline.
- Part of a series of stages executed by the slot-based engine that
occurs at the beginning of the pipeline. For example, if a pipeline
$groupstages are executed by the slot-based engine.
In most cases, the slot-based engine provides improved performance and lower CPU and memory costs compared to the classic query engine.
Starting in MongoDB 5.2, time series collection data is further compressed to save database space. This compression does not affect query results, nor does it negatively affect performance.
Starting in MongoDB 5.2, the time that a
started is included in the:
Starting in MongoDB 5.2, the default chunk size is 128 megabytes. In earlier versions of MongoDB, the default chunk size is 64 megabytes.
Starting in MongoDB 5.2, the
Starting in MongoDB 5.2 (and 5.0.4, 5.1.0)
parameter limits the time a shard waits for a critical section within a
Starting in MongoDB 5.2, you can use the following new server parameters to configure the refresh interval for cached LDAP user information:
Starting in MongoDB 5.2, the update interval for cached user information
retrieved from an LDAP server depends on
Starting in MongoDB 5.2, you can omit
customData from the response
To omit custom data from command output, specify the
initialSyncMethod is only available in MongoDB Enterprise
To report an issue, see https://github.com/mongodb/mongo/wiki/Submit-Bug-Reports for instructions on how to file a JIRA ticket for the MongoDB server or one of the related projects.