Release Notes for MongoDB 7.0MongoDB 7.0发布说明

mongosh Methodsmongosh方法

Database Commands数据库命令

Aggregation Stages聚合阶段

Cache Refresh Time Fields缓存刷新时间字段

Starting in MongoDB 7.0, log messages for slow queries includes a new cache refresh time field.从MongoDB 7.0开始，慢速查询的日志消息包括一个新的缓存刷新时间字段。

Concurrent Storage Engine Transactions并发存储引擎事务

Starting in MongoDB 7.0, an algorithm that dynamically adjusts the number of concurrent storage engine transactions is enabled by default.从MongoDB 7.0开始，默认情况下会启用一种动态调整并发存储引擎事务数的算法。

To learn more, see wiredTiger.concurrentTransactions, wiredTigerConcurrentReadTransactions, and wiredTigerConcurrentWriteTransactions.要了解更多信息，请参阅wiredTiger.concurrentTransactions、wiredTigerConcurrentReadTransactions和wiredTigerConcurrentWriteTransactions。

currentOp Metrics度量

Starting in MongoDB 7.0, the currentOp command and the db.currentOp() method include these new fields:从MongoDB 7.0开始，currentOp命令和db.currentOp()方法包括以下新字段：

• currentOp.admissionPriority
• currentOp.collUuid
• currentOp.startTime
• currentOp.samplesPerSecond
• currentOp.sampledReadsCount
• currentOp.sampledWritesCount
• currentOp.sampledReadsBytes
• currentOp.sampledWritesBytes

$currentOp (aggregation) Metrics（聚合）度量

Starting in MongoDB 7.0, the currentOp aggregation stage includes these new fields:从MongoDB 7.0开始，currentOp聚合阶段包括以下新字段：

• $currentOp.collUuid
• $currentOp.startTime
• $currentOp.samplesPerSecond
• $currentOp.sampledReadsCount
• $currentOp.sampledWritesCount
• $currentOp.sampledReadsBytes
• $currentOp.sampledWritesBytes

Compound Wildcard Indexes复合通配符索引

Starting in MongoDB 7.0, you can create compound wildcard indexes. 从MongoDB 7.0开始，您可以创建复合通配符索引。A compound wildcard index has one wildcard term and one or more additional index terms.复合通配符索引具有一个通配符项和一个或多个附加索引项。

Use compound wildcard indexes to support queries on known patterns and to limit the total number of indexes in a collection.使用复合通配符索引可以支持对已知模式的查询，并限制集合中的索引总数。

Large Change Stream Events大型变更流事件

Starting in MongoDB 7.0, if you have change stream events larger than 16 MB, you can use the new $changeStreamSplitLargeEvent stage to split the events into smaller fragments.从MongoDB 7.0开始，如果您有大于16 MB的更改流事件，您可以使用新的$changeStreamSplitLargeEvent阶段将事件拆分为更小的片段。

The following new metrics report information about large change stream events:以下新指标报告了有关大型变更流事件的信息：

• metrics.changeStreams
• metrics.changeStreams.largeEventsFailed
• metrics.changeStreams.largeEventsSplit

Slot-Based Query Execution Engine基于插槽的查询执行引擎

Starting in MongoDB 7.0, the slot-based query execution engine improves performance for a wider range of find and aggregation queries.从MongoDB 7.0开始，基于槽的查询执行引擎提高了更广泛的查找和聚合查询的性能。

Slow query log messages慢速查询日志消息 now include a queryFramework field that indicates which query engine completed the query:现在包括一个queryFramework字段，该字段指示哪个查询引擎完成了查询：

• queryFramework: "classic" indicates that the classic engine completed the query.指示经典引擎完成了查询。
• queryFramework: "sbe" indicates that the slot-based query execution engine completed the query.指示基于槽的查询执行引擎完成了查询。

User Roles System Variable用户角色系统变量

Starting in MongoDB 7.0, you can use the new USER_ROLES system variable to return the roles of the current user.从MongoDB 7.0开始，您可以使用新的USER_ROLES系统变量来返回当前用户的角色。

For use cases that include USER_ROLES, see the find, aggregation, view, updateOne, updateMany, and findAndModify examples.有关包括USER_ROLES的用例，请参阅find、aggregation、view、updateOne、updateMany和findAndModify示例。

New Sharding Statistics for Chunk Migrations块迁移的新分片统计

Available starting in MongoDB 7.0 (and 6.3.2, 6.0.6, and 5.0.18).从MongoDB 7.0（以及6.3.2、6.0.6和5.0.18）开始提供。

MongoDB includes the following new sharding statistics for chunk migrations:MongoDB为区块迁移提供了以下新的分片统计信息：

• shardingStatistics.countDonorMoveChunkCommitted
• shardingStatistics.countDonorMoveChunkAborted
• shardingStatistics.totalDonorMoveChunkTimeMillis
• shardingStatistics.countBytesClonedOnRecipient
• shardingStatistics.countDocsClonedOnCatchUpOnRecipient
• shardingStatistics.countBytesClonedOnCatchUpOnRecipient

New Slow Query Log Message新建慢速查询日志消息

Starting in MongoDB 7.0, the totalOplogSlotDurationMicros in the slow query log message shows the time between a write operation getting a commit timestamp to commit the storage engine writes and actually committing. mongod supports parallel writes. However, it commits write operations with commit timestamps in any order.从MongoDB 7.0开始，慢速查询日志消息中的totalOplogSlotDurationMicros显示了写入操作获得提交存储引擎写入的提交时间戳与实际提交之间的时间。mongod支持并行写入。但是，它以任何顺序提交带有提交时间戳的写操作。

To learn more, see Logging Slow Operations.要了解更多信息，请参阅记录慢速操作。

New Parameters新建参数

Queryable Encryption General Availability可查询加密常规可用性

Starting in MongoDB 7.0, Queryable Encryption with equality queries is generally available (GA). 从MongoDB 7.0开始，通常可以使用具有相等查询的可查询加密。Improvements in the GA make it incompatible with the Queryable Encryption Public Preview, which should not be used now that the feature is GA. GA中的改进使其与Queryable Encryption Public Preview不兼容，因为该功能已经是GA，所以不应该使用它。For details, see Compatibility Changes in MongoDB 7.0.有关详细信息，请参阅MongoDB 7.0中的兼容性更改。

KMIP 1.0 and 1.1 SupportKMIP 1.0和1.1支持

MongoDB 7.0 (and 6.0.6) adds the useLegacyProtocol setting. MongoDB 7.0（和6.0.6）添加了useLegacyProtocol设置。This setting allows MongoDB servers to connect to KMIP servers that use KMIP protocol version 1.0 or 1.1.此设置允许MongoDB服务器连接到使用KMIP协议版本1.0或1.1的KMIP服务器。

mergeAllChunksOnShard Command命令

Starting in MongoDB 7.0, the mergeAllChunksOnShard command finds and merges all mergeable chunks that a shard owns for a given collection.从MongoDB 7.0开始，mergeAllChunksOnShard命令查找并合并一个分片为给定集合拥有的所有可合并块。

The AutoMerger自动合并

Starting in MongoDB 7.0, the AutoMerger can automatically merge chunks that meet the mergeability requirements. 从MongoDB 7.0开始，AutoMerger可以自动合并满足可合并性要求的块。The AutoMerger is enabled by default.自动合并在默认情况下处于启用状态。

Starting in MongoDB 7.0, you can use the following methods to control the AutoMerger behavior:从MongoDB 7.0开始，您可以使用以下方法来控制AutoMerger行为：

• sh.startAutoMerger()
• sh.stopAutoMerger()
• sh.enableAutoMerger()
• sh.disableAutoMerger()

enableAutoMerger Parameter for configureCollectionBalancingenableAutoMerger参数用于configureCollectionBalancing

Starting in MongoDB 7.0, the configureCollectionBalancing command accepts the enableAutoMerger parameter. 从MongoDB 7.0开始，configureCollectionBalancing命令接受enableAutoMerger参数。Use enableAutoMerger to set whether or not the AutoMerger takes this collection into account.使用enableAutoMerger设置AutoMerger是否考虑此集合。

rangeDeleterHighPriority Parameter for Deprioritizing Range deletions参数用于取消范围删除优先级

Starting in MongoDB 7.0, you can prioritize or deprioritize cleanup of orphaned documents over user operations using the rangeDeleterHighPriority parameter.从MongoDB 7.0开始，您可以使用rangeDeleterHighPriority参数将孤立文档的清理优先级设置为高于用户操作的优先级或取消优先级。

operationsBlockedByRefresh Metrics Removed已删除度量

MongoDB 7.0 removes the operationsBlockedByRefresh document that contains statistics about operations blocked by catalog cache refresh activity because the operationsBlockedByRefresh counters increased on mongos for every operation that used collection routing information even if the operation wasn't blocked by a catalog refresh activity.MongoDB 7.0删除了operationsBlockedByRefresh文档，该文档包含有关目录缓存刷新活动阻止的操作的统计信息，因为对于每个使用集合路由信息的操作，即使该操作没有被目录刷新活动阻止，mongos上的operationsBlockedByRefresh计数器也会增加。

analyzeShardKey Command and 命令和db.collection.analyzeShardKey() Method方法

MongoDB 7.0 adds the analyzeShardKey command and the db.collection.analyzeShardKey() method, which let you calculate metrics for evaluating a shard key.MongoDB 7.0添加了analyzeShardKey命令和db.collection.analyzeShardKey()方法，可以计算评估分片键的指标。

configureQueryAnalyzer Command and 命令和db.collection.configureQueryAnalyzer() Method方法

MongoDB 7.0 adds the configureQueryAnalyzer command, which allows you to configure query sampling for a collection. MongoDB 7.0添加了configureQueryAnalyzer命令，该命令允许您为集合配置查询采样。MongoDB 7.0 also adds the db.collection.configureQueryAnalyzer(), which wraps the configureQueryAnalyzer command. Sampled queries provide information to analyzeShardKey to calculate metrics about read and write distribution of a shard key.MongoDB 7.0还添加了db.collection.configureQueryAnalyzer()，它封装了configQueryAnalyzer命令。采样查询为analyzeShardKey提供信息，以计算有关分片键的读写分布的度量。

serverStatus Output Change输出更改

serverStatus includes the following new fields in its output:在其输出中包括以下新字段：

Plan Cache Metrics计划缓存指标

• planCache

queryAnalyzer MetricsqueryAnalyzer度量

• queryAnalyzers.activeCollections
• queryAnalyzers.totalCollections
• queryAnalyzers.totalSampledReadsCount
• queryAnalyzers.totalSampledWritesCount
• queryAnalyzers.totalSampledReadsBytes
• queryAnalyzers.totalSampledWritesBytes

Removed Platforms拆除的平台

MongoDB 7.0 removes support for RHEL 7 / CentOS 7 / Oracle 7 on the PPC64LE and s390x architectures.

Only Single-Version Downgrades are Supported仅支持单一版本降级

MongoDB only supports single-version downgrades. MongoDB只支持单版本降级。You cannot downgrade to a release that is multiple versions behind your current release.您不能降级到比当前版本落后多个版本的版本。

For example, you may downgrade a 7.0-series to a 6.0-series deployment. 例如，您可以将7.0系列部署降级为6.0系列部署。However, further downgrading that 6.0-series deployment to a 5.0-series deployment is not supported.但是，不支持将6.0系列部署进一步降级为5.0系列部署。

Downgrade Policy Changes降级策略更改

Starting in MongoDB 7.0:在MongoDB 7.0中启动：

• Binary downgrades are no longer supported for MongoDB Community Edition.MongoDB社区版不再支持二进制降级。
• You cannot downgrade your deployment's fCV to or from a rapid release version of MongoDB.您不能将部署的fCV降级到MongoDB的快速发布版本或从快速发布版本降级。
• The setFeatureCompatibilityVersion command requires an additional parameter, confirm, which must be set to true to upgrade or downgrade fCV.setFeatureCompatibilityVersion命令需要一个额外的参数confirm，该参数必须设置为true才能升级或降级fCV。
• If you upgrade or downgrade your deployment's fCV, you cannot downgrade your Enterprise deployment's binary version without assistance from support.如果升级或降级部署的fCV，则在没有支持的帮助下无法降级企业部署的二进制版本。

Backward-Incompatible Features向后不兼容的功能

MongoDB 7.0 includes features that are not compatible with earlier releases. MongoDB 7.0包含与早期版本不兼容的功能。Downgrading from 7.0 to an earlier release requires that you remove data that uses these features.从7.0降级到早期版本需要删除使用这些功能的数据。

For more information, see Backward-Incompatible Features.有关详细信息，请参阅向后不兼容功能。