Definition定义
db.collection.replaceOne(filter, replacement, options)Replaces a single document within the collection based on the filter.根据筛选器替换集合中的单个文档。Returns:返回A document containing:包含以下内容的文档:A boolean如果操作在写入关注下运行,则布尔值acknowledgedastrueif the operation ran with write concern orfalseif write concern was disabledacknowledged为true,如果写入关注被禁用,则确认为falsematchedCountcontaining the number of matched documents包含匹配文档的数量modifiedCountcontaining the number of modified documents包含已修改文档的数量upsertedIdcontaining the包含已更新文档的_idfor 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()方法接受以下参数:
filter |
| |
replacement |
| |
upsert |
| |
writeConcern |
| |
collation |
| |
hint |
| |
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
upsert on a Sharded CollectionA 在分片集合上包含db.collection.replaceOne() operation that includes upsert: true on a sharded collection must include the full shard key in the filter.upsert: true的db.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 keyShard 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:此外,以下要求也适用:
nullnull |
|
null valuenull值 |
|
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 Upsertupsert: 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:w为majority,wtimeout为100:
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的可能值:
clientSupplied | |
customDefault | setDefaultRWConcern.setDefaultRWConcern。 |
getLastErrorDefaults | settings.getLastErrorDefaults field.settings.getLastErrorDefaults字段。 |
implicitDefault |
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指定replaceOne的hint
hint for replaceOneCreate 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查找ratingof4, which are"Pizza Place"and"Taco Shop".rating为4的餐厅,分别是"Pizza Place"和"Taco Shop"。Sorts the found restaurants by按violationsin 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 }
]