Database Manual / Reference / mongosh Methods / Collections

db.collection.replaceOne() (mongosh method方法)

Definition定义

db.collection.replaceOne(filter, replacement, options)

Replaces a single document within the collection based on the filter.根据筛选器替换集合中的单个文档。

Returns:返回A document containing: 包含以下内容的文档:
  • A boolean acknowledged as true if the operation ran with write concern or false if write concern was disabled如果操作在写入关注下运行,则布尔值acknowledgedtrue,如果写入关注被禁用,则确认为false
  • matchedCount containing the number of matched documents包含匹配文档的数量
  • modifiedCount containing the number of modified documents包含已修改文档的数量
  • upsertedId containing the _id for the upserted document包含已更新文档的_id

Compatibility兼容性

This method is available in deployments hosted in the following environments:此方法在以下环境中托管的部署中可用:

  • MongoDB Atlas: The fully managed service for MongoDB deployments in the cloud:云中MongoDB部署的完全托管服务

Note

This command is supported in all MongoDB Atlas clusters. 所有MongoDB Atlas集群都支持此命令。For information on Atlas support for all commands, see Unsupported Commands.有关Atlas支持所有命令的信息,请参阅不支持的命令

  • MongoDB Enterprise: The subscription-based, self-managed version of MongoDB:MongoDB的基于订阅的自我管理版本
  • MongoDB Community: The source-available, free-to-use, and self-managed version of MongoDB:MongoDB的源代码可用、免费使用和自我管理版本

Syntax语法

Changed in version 8.0.在版本8.0中的更改。

The replaceOne() method has the following form:replaceOne()方法具有以下形式:

db.collection.replaceOne(
<filter>,
<replacement>,
{
upsert: <boolean>,
writeConcern: <document>,
collation: <document>,
hint: <document|string>,
sort: <document>
}
)

The replaceOne() method takes the following parameters:replaceOne()方法接受以下参数:

Parameter参数Type类型Description描述
filterdocument文档

The selection criteria for the update. The same query selectors as in the find() method are available.更新的选择标准。可以使用与find()方法中相同的查询选择器

Specify an empty document { } to replace the first document returned in the collection.指定一个空文档{ }以替换集合中返回的第一个文档。

replacementdocument文档

The replacement document.替换文件。

Cannot contain update operators.不能包含更新运算符

upsertboolean布尔值

Optional. 可选。When true, replaceOne() either:如果为true,则replaceOne()会出现以下两种情况:

  • Inserts the document from the replacement parameter if no document matches the filter.如果没有文档与filter匹配,则从replacement参数插入文档。
  • Replaces the document that matches the filter with the replacement document.replacement文档替换与filter匹配的文档。

MongoDB will add the _id field to the replacement document if it is not specified in either the filter or replacement documents. If _id is present in both, the values must be equal.如果未在筛选器或替换文档中指定_id字段,MongoDB会将其添加到替换文档中。如果_id同时存在于两者中,则值必须相等。

To avoid multiple upserts, ensure that the query fields are uniquely indexed.为了避免多个upsert,请确保query字段具有唯一索引

Defaults to false.默认为false

writeConcerndocument文档

Optional. 可选。A document expressing the write concern. Omit to use the default write concern.表达写入关注的文件。省略使用默认写入关注。

Do not explicitly set the write concern for the operation if run in a transaction. To use write concern with transactions, see Transactions and Write Concern.如果在事务中运行,则不要显式设置操作的写入关注。要对事务使用写关注,请参阅事务和写关注

collationdocument文档

Optional.可选。

Specifies the collation to use for the operation.指定用于操作的排序规则

Collation allows users to specify language-specific rules for string comparison, such as rules for lettercase and accent marks.排序规则允许用户为字符串比较指定特定于语言的规则,例如字母大小写和重音标记的规则。

The collation option has the following syntax:排序规则选项具有以下语法:

collation: {
locale: <string>,
caseLevel: <boolean>,
caseFirst: <string>,
strength: <int>,
numericOrdering: <boolean>,
alternate: <string>,
maxVariable: <string>,
backwards: <boolean>
}

When specifying collation, the locale field is mandatory; all other collation fields are optional. For descriptions of the fields, see Collation Document.指定排序规则时,locale字段是必填的;所有其他排序字段都是可选的。有关字段的描述,请参阅排序规则文档

If the collation is unspecified but the collection has a default collation (see db.createCollection()), the operation uses the collation specified for the collection.如果未指定排序规则,但集合具有默认排序规则(请参阅db.createCollection()),则操作将使用为集合指定的排序规则。

If no collation is specified for the collection or for the operations, MongoDB uses the simple binary comparison used in prior versions for string comparisons.如果没有为集合或操作指定排序规则,MongoDB将使用以前版本中用于字符串比较的简单二进制比较。

You cannot specify multiple collations for an operation. For example, you cannot specify different collations per field, or if performing a find with a sort, you cannot use one collation for the find and another for the sort.不能为操作指定多个排序规则。例如,您不能为每个字段指定不同的排序规则,或者如果使用排序执行查找,则不能对查找使用一个排序规则,对排序使用另一个。

hintdocument文档

Optional. 可选。A document or string that specifies the index to use to support the filter.指定用于支持筛选器索引的文档或字符串。

The option can take an index specification document or the index name string.该选项可以采用索引规范文档或索引名称字符串。

If you specify an index that does not exist, the operation errors.如果指定的索引不存在,则操作会出错。

For an example, see Specify hint for replaceOne.例如,请参阅指定replaceOnehint

sortdocument文档

Optional.可选。

Orders the documents before the update is applied.在应用更新之前订购文档。

If the sort argument is not a document, the operation errors.如果排序参数不是文档,则操作会出错。

MongoDB does not store documents in a collection in a particular order. When sorting on a field which contains duplicate values, documents containing those values may be returned in any order.MongoDB不会以特定顺序将文档存储在集合中。在对包含重复值的字段进行排序时,包含这些值的文档可以按任何顺序返回。

The $sort operation is not a "stable sort," which means that documents with equivalent sort keys are not guaranteed to remain in the same relative order in the output as they were in the input.$sort操作不是“稳定排序”,这意味着具有等效排序键的文档不能保证在输出中保持与输入中相同的相对顺序。

If the field specified in the sort criteria does not exist in two documents, then the value on which they are sorted is the same. The two documents may be returned in any order.如果排序条件中指定的字段在两个文档中不存在,则对它们进行排序的值是相同的。这两份文件可以按任何顺序退回。

If consistent sort order is desired, include at least one field in your sort that contains unique values. The easiest way to guarantee this is to include the _id field in your sort query.如果需要一致的排序顺序,请在排序中至少包含一个包含唯一值的字段。保证这一点的最简单方法是在排序查询中包含_id字段。

For more information, see Sort Consistency.有关详细信息,请参阅排序一致性

New in version 8.0.在版本8.0中新增。

For an example, see Replace One Document and Use a Sort.例如,请参阅替换一个文档并使用排序

Behavior行为

replaceOne() replaces the first matching document in the collection that matches the filter, using the replacement document.使用replacement文档替换集合中与filter匹配的第一个匹配文档。

upsert

If upsert: true and no documents match the filter, db.collection.replaceOne() creates a new document based on the replacement document.如果upsert: true且没有文档与filter匹配,db.collection.replaceOne()将根据replacement文档创建一个新文档。

If you specify upsert: true on a sharded collection, you must include the full shard key in the filter. 如果在分片集合上指定upsert: true,则必须在filter中包含完整的分片键。For additional db.collection.replaceOne() behavior on a sharded collection, see Sharded Collections.有关分片集合上的其他db.collection.replaceOne()行为,请参阅分片集合

See Replace with Upsert.请参阅用Upsert替换

Capped Collections封顶集合

If a replacement operation changes the document size, the operation will fail.如果替换操作更改了文档大小,则操作将失败。

Time Series Collections时间序列集合

You cannot use the replaceOne() method on a time series collection.您不能在时间序列集合上使用replaceOne()方法。

Sharded Collections分片化集合

db.collection.replaceOne() attempts to target a single shard, first by using the query filter. If the operation cannot target a single shard by the query filter, it then attempts to target by the replacement document.尝试首先使用查询筛选器来定位单个分片。如果操作无法通过查询筛选器定位单个分片,则它会尝试通过替换文档定位。

In earlier versions, the operation attempts to target using the replacement document.在早期版本中,该操作尝试使用替换文档作为目标。

Shard Key Requirements In Replacement Document替换文件中的关键要求

The replacement document does not need to include the shard key.替换文档不需要包含分片键。

Warning

Documents in sharded collections can be missing the shard key fields. Take precaution to avoid accidentally removing the shard key when changing a document's shard key value.分片集合中的文档可能缺少分片键字段。采取预防措施,避免在更改文档的分片键值时意外删除分片键。

upsert on a Sharded Collection分片系列的upsert

A db.collection.replaceOne() operation that includes upsert: true on a sharded collection must include the full shard key in the filter.在分片集合上包含upsert: truedb.collection.replaceOne()操作必须在filter中包含完整的分片键。

However, documents in a sharded collection can be missing the shard key fields. To target a document that is missing the shard key, you can use the null equality match in conjunction with another filter condition (such as on the _id field). For example:但是,分片集合中的文档可能会缺少分片键字段。要针对缺少分片键的文档,您可以将空相等匹配与另一个筛选条件结合使用(例如在_id字段上)。例如:

{ _id: <value>, <shardkeyfield>: null } // _id of the document missing shard key

Shard Key Modification分片键修改

You can update a document's shard key value unless the shard key field is the immutable _id field.您可以更新文档的分片键值,除非分片键字段是不可变的_id字段。

Warning

Documents in sharded collections can be missing the shard key fields. Take precaution to avoid accidentally removing the shard key when changing a document's shard key value.分片集合中的文档可能缺少分片键字段。采取预防措施,避免在更改文档的分片键值时意外删除分片键。

To modify the existing shard key value with db.collection.replaceOne():要使用db.collection.replaceOne()修改现有的分片键值,请执行以下操作:

  • You must run on a mongos. Do not issue the operation directly on the shard.必须在mongos上运行。不要直接在分片上执行操作。
  • You must run either in a transaction or as a retryable write.您必须在事务中运行或作为可重试写入运行。
  • You must include an equality filter on the full shard key.您必须在完整分片键上包含相等filter

Missing Shard Key缺少分片钥匙

Documents in a sharded collection can be missing the shard key fields. 分片集合中的文档可能缺少分片键字段To use db.collection.replaceOne() to set the document's missing shard key, you must run on a mongos. Do not issue the operation directly on the shard.要使用db.collection.replaceOne()设置文档缺少的分片键,您必须在mongos上运行。不要直接在分片上执行操作。

In addition, the following requirements also apply:此外,以下要求也适用:

Task任务Requirements需求
To set to null设置为null
  • Requires equality filter on the full shard key if upsert: true is specified.如果指定了upsert: true,则需要对完整分片键进行相等筛选器。
To set to a non-null value设置为非null
  • Must be performed either inside a transaction or as a retryable write.必须在事务内部或作为可重试写入执行。
  • Requires equality filter on the full shard key if either:在以下任一情况下,需要对完整分片键进行相等筛选器:

    • upsert: true, or,或
    • the new shard key value belongs to a different shard.新的分片键值属于不同的分片。

Tip

Since a missing key value is returned as part of a null equality match, to avoid updating a null-valued key, include additional query conditions (such as on the _id field) as appropriate.由于缺少的键值是作为空相等匹配的一部分返回的,为了避免更新null值键值,请酌情包含其他查询条件(例如在_id字段上)。

See also:另请参阅:

Transactions事务

db.collection.replaceOne() can be used inside distributed transactions.可以在分布式事务中使用。

Important

In most cases, a distributed transaction incurs a greater performance cost over single document writes, and the availability of distributed transactions should not be a replacement for effective schema design. 在大多数情况下,分布式事务比单文档写入产生更大的性能成本,分布式事务的可用性不应取代有效的模式设计。For many scenarios, the denormalized data model (embedded documents and arrays) will continue to be optimal for your data and use cases. 对于许多场景,非规范化数据模型(嵌入式文档和数组)将继续是数据和用例的最佳选择。That is, for many scenarios, modeling your data appropriately will minimize the need for distributed transactions.也就是说,对于许多场景,适当地对数据进行建模将最大限度地减少对分布式事务的需求。

For additional transactions usage considerations (such as runtime limit and oplog size limit), see also Production Considerations.有关其他事务使用注意事项(如运行时限制和oplog大小限制),另请参阅生产注意事项

Upsert within Transactions事务中的失误

You can create collections and indexes inside a distributed transaction if the transaction is not a cross-shard write transaction.如果分布式事务不是跨分片写入事务,则可以在该事务内创建集合和索引。

db.collection.replaceOne() with upsert: true can be run on an existing collection or a non-existing collection. db.collection.replaceOne()配合upsert: true可以在现有集合或不存在的集合上运行。If run on a non-existing collection, the operation creates the collection.如果在不存在的集合上运行,则该操作将创建该集合。

Write Concerns and Transactions撰写入关注和事务

Do not explicitly set the write concern for the operation if run in a transaction. To use write concern with transactions, see Transactions and Write Concern.如果在事务中运行,则不要显式设置操作的写入关注。要对事务使用写关注,请参阅事务和写关注

Examples示例

Replace替换

The restaurant collection contains the following documents:restaurant集合包含以下文件:

db.restaurant.insertMany ( [
{ _id: 1, name: "Central Perk Cafe", Borough: "Manhattan" },
{ _id: 2, name: "Rock A Feller Bar and Grill", Borough: "Queens", violations: 2 },
{ _id: 3, name: "Empire State Pub", Borough: "Brooklyn", violations: 0 }
] )

The following operation replaces a single document where name: "Central Perk Cafe":以下操作将替name: "Central Perk Cafe"的单个文档:

try {
db.restaurant.replaceOne(
{ "name" : "Central Perk Cafe" },
{ "name" : "Central Pork Cafe", "Borough" : "Manhattan" }
);
} catch (e){
print(e);
}

The operation returns:操作返回:

{ "acknowledged" : true, "matchedCount" : 1, "modifiedCount" : 1 }

If no matches were found, the operation instead returns:如果没有找到匹配项,则操作将返回:

{ "acknowledged" : true, "matchedCount" : 0, "modifiedCount" : 0 }

Setting upsert: true would insert the document if no match was found. See Replace with Upsert如果未找到匹配项,设置upsert: true将插入文档。请参阅更换为Upsert

Replace with Upsert替换为Upsert

The restaurant collection contains the following documents:restaurant集合包含以下文件:

db.restaurant.insertMany( [
{ _id: 1, name: "Central Perk Cafe", Borough: "Manhattan", violations: 3 },
{ _id: 2, name: "Rock A Feller Bar and Grill", Borough: "Queens", violations: 2 },
{ _id: 3, name: "Empire State Pub", Borough: "Brooklyn", violations: 0 }
] )

The following operation attempts to replace the document with name : "Pizza Rat's Pizzaria", with upsert : true:以下操作尝试将文档替换为name : "Pizza Rat's Pizzaria",并使用upsert : true

try {
db.restaurant.replaceOne(
{ "name" : "Pizza Rat's Pizzaria" },
{ "_id": 4, "name" : "Pizza Rat's Pizzaria", "Borough" : "Manhattan", "violations" : 8 },
{ upsert: true }
);
} catch (e){
print(e);
}

Since upsert : true the document is inserted based on the replacement document. The operation returns:由于upsert:true,文档将根据replacement文档插入。操作返回:

{
"acknowledged" : true,
"matchedCount" : 0,
"modifiedCount" : 0,
"upsertedId" : 4
}

The collection now contains the following documents:该集合现在包含以下文档:

{ _id: 1, name: "Central Perk Cafe", Borough: "Manhattan", violations: 3 },
{ _id: 2, name: "Rock A Feller Bar and Grill", Borough: "Queens", violations: 2 },
{ _id: 3, name: "Empire State Pub", Borough: "Brooklyn", violations: 0 },
{ _id: 4, name: "Pizza Rat's Pizzaria", Borough: "Manhattan", violations: 8 }

Replace with Write Concern替换为写入关注

Given a three member replica set, the following operation specifies a w of majority and wtimeout of 100:给定一个由三个成员组成的副本集,以下操作指定wmajoritywtimeout100

try {
db.restaurant.replaceOne(
{ "name" : "Pizza Rat's Pizzaria" },
{ "name" : "Pizza Rat's Pub", "Borough" : "Manhattan", "violations" : 3 },
{ w: "majority", wtimeout: 100 }
);
} catch (e) {
print(e);
}

If the acknowledgment takes longer than the wtimeout limit, the following exception is thrown:如果确认时间超过wtimeout限制,则抛出以下异常:

WriteConcernError({
"code" : 64,
"errmsg" : "waiting for replication timed out",
"errInfo" : {
"wtimeout" : true,
"writeConcern" : {
"w" : "majority",
"wtimeout" : 100,
"provenance" : "getLastErrorDefaults"
}
}
})

The following table explains the possible values of errInfo.writeConcern.provenance:下表解释了errInfo.writeConcern.provenance的可能值:

Provenance来源Description描述
clientSuppliedThe write concern was specified in the application.应用程序中指定了写入关注。
customDefaultThe write concern originated from a custom defined default value. See setDefaultRWConcern.写入关注源于自定义的默认值。请参阅setDefaultRWConcern
getLastErrorDefaultsThe write concern originated from the replica set's settings.getLastErrorDefaults field.写入关注源于副本集的settings.getLastErrorDefaults字段。
implicitDefaultThe write concern originated from the server in absence of all other write concern specifications.在没有所有其他写入关注规范的情况下,写入关注源自服务器。

Specify Collation指定排序规则

Collation allows users to specify language-specific rules for string comparison, such as rules for lettercase and accent marks.排序规则允许用户为字符串比较指定特定于语言的规则,例如字母大小写和重音标记的规则。

A collection myColl has the following documents:

db.myColl.insertMany( [
{ _id: 1, category: "café", status: "A" },
{ _id: 2, category: "cafe", status: "a" },
{ _id: 3, category: "cafE", status: "a" }
] )

The following operation includes the collation option:以下操作包括排序规则选项:

db.myColl.replaceOne(
{ category: "cafe", status: "a" },
{ category: "cafÉ", status: "Replaced" },
{ collation: { locale: "fr", strength: 1 } }

);

Specify hint for replaceOne指定replaceOnehint

Create a sample members collection with the following documents:使用以下文档创建示例members集合:

db.members.insertMany( [
{ _id: 1, member: "abc123", status: "P", points: 0, misc1: null, misc2: null },
{ _id: 2, member: "xyz123", status: "A", points: 60, misc1: "reminder: ping me at 100pts", misc2: "Some random comment" },
{ _id: 3, member: "lmn123", status: "P", points: 0, misc1: null, misc2: null },
{ _id: 4, member: "pqr123", status: "D", points: 20, misc1: "Deactivated", misc2: null },
{ _id: 5, member: "ijk123", status: "P", points: 0, misc1: null, misc2: null },
{ _id: 6, member: "cde123", status: "A", points: 86, misc1: "reminder: ping me at 100pts", misc2: "Some random comment" }
] )

Create the following indexes on the collection:在集合上创建以下索引:

db.members.createIndex( { status: 1 } )
db.members.createIndex( { points: 1 } )

The following update operation explicitly hints to use the index { status: 1 }:以下更新操作明确提示使用索引{ status: 1 }

Note

If you specify an index that does not exist, the operation errors.如果指定的索引不存在,则操作会出错。

db.members.replaceOne(
{ "points": { $lte: 20 }, "status": "P" },
{ "misc1": "using index on status", status: "P", member: "replacement", points: "20"},
{ hint: { status: 1 } }
)

The operation returns the following:该操作返回以下内容:

{ "acknowledged" : true, "matchedCount" : 1, "modifiedCount" : 1 }

To view the indexes used, you can use the $indexStats pipeline:要查看使用的索引,可以使用$indexStats管道:

db.members.aggregate( [ { $indexStats: { } }, { $sort: { name: 1 } } ] )

Replace One Document and Use a Sort替换一个文档并使用排序

Create the following restaurantsSort collection:创建以下restaurantsSort集合:

db.restaurantsSort.insertMany( [
{ _id: 1, name: "Pizza Place", rating: 4, violations: 2 },
{ _id: 2, name: "Burger Joint", rating: 3, violations: 5 },
{ _id: 3, name: "Taco Shop", rating: 4, violations: 1 }
] )

The following example replaces "Pizza Place" with "Clean Eats":以下示例将"Pizza Place"替换为"Clean Eats"

db.restaurantsSort.replaceOne(
// Find restaurants with a rating of 4
{ rating: 4 },

// Replace the found restaurant with Clean Eats
{ name: "Clean Eats", rating: 4, violations: 2 },

// Sort restaurants found by the most violations with a descending sort
{ sort: { violations: -1 } }
)

The example:示例:

  • Finds restaurants with a rating of 4, which are "Pizza Place" and "Taco Shop".查找rating4的餐厅,分别是"Pizza Place""Taco Shop"
  • Sorts the found restaurants by violations in descending order, which places "Pizza Place" in the first position.violations(违规行为)降序排列找到的餐厅,将"Pizza Place"放在第一位。
  • Replaces "Pizza Place" with "Clean Eats"."Pizza Place"替换为"Clean Eats"

The following query returns the restaurants:以下查询返回餐厅:

db.restaurantsSort.find()

Output shows "Pizza Place" was replaced with "Clean Eats":输出显示"Pizza Place"被替换为"Clean Eats"

[
{ _id: 1, name: 'Clean Eats', rating: 4, violations: 2 },
{ _id: 2, name: 'Burger Joint', rating: 3, violations: 5 },
{ _id: 3, name: 'Taco Shop', rating: 4, violations: 1 }
]