Release Notes for MongoDB 7.3
On this page
Important
MongoDB 7.3 is a rapid release and is only supported for MongoDB Atlas. MongoDB 7.3 is not supported for use on-premises. For more information, see MongoDB Versioning.
Patch Releases
7.3.3 - Jun 11, 2024
Issues fixed:
SERVER-78556 Return default of
internalInsertMaxBatchSizeto 64SERVER-83712 Do not add
$inlength to plan cache key if there is no sortSERVER-86674 Primary catch-up may believe it is caught up when it is not
SERVER-87961 Time series
$grouprewrite may produce incorrect results when a preceding$projectstage projects out accessed fields
7.3.2 - Apr 30, 2024
Issues fixed:
SERVER-82349: Mongo 7 crashes on applyOps index delete/drops without a collection UUID
SERVER-85892: $merge with pipeline after $documents returns error
SERVER-86583: Non-transactional snapshot read on unsharded collection may execute with mismatched sharding metadata
SERVER-88173: BinData bit comparisons give wrong results in many cases
WT-10807: Skip in-memory deleted pages as part of the tree walk
7.3.1 - Apr 4, 2024
Issues fixed:
SERVER-87191 Update without shard key might miss documents
SERVER-88360 Remove "Sharding catalog and local catalog collection uuid do not match" tripwire assertion
General Changes
Compaction Improvements
Starting in MongoDB 7.3, the compact command includes a new
freeSpaceTargetMB option to specify the minimum amount of storage space, in
megabytes, that must be recoverable for compaction to proceed.
Find Cursor Behavior on Views
Starting in MongoDB 7.3, when you use a find command on a view
with the singleBatch: true and batchSize: 1 options, a cursor
is no longer returned. In previous versions of MongoDB these find queries
would return a cursor even when you set the single batch
option to true.
serverStatus Metrics
Starting in MongoDB 7.3, the serverStatus command output
includes the following new metrics: