On this page本页内容
db.collection.replaceOne(filter, replacement, options)
This is a mongosh
method. This is not the documentation for Node.js
or other programming language specific driver methods.
In most cases, mongosh
methods work the same way as the legacy mongo
shell methods. However, some legacy methods are unavailable in mongosh
.
For the legacy mongo
shell documentation, refer to the documentation for the corresponding MongoDB Server release:
For MongoDB API drivers, refer to the language specific MongoDB driver documentation.
Replaces a single document within the collection based on the filter.基于筛选器替换集合中的单个文档。
The replaceOne()
method has the following form:replaceOne()
方法具有以下形式:
db.collection.replaceOne( <filter>, <replacement>, { upsert: <boolean>, writeConcern: <document>, collation: <document>, hint: <document|string> // Available starting in 4.2.1 } )
The replaceOne()
method takes the following parameters:replaceOne()
方法采用以下参数:
filter | document |
|
replacement | document |
|
upsert | boolean |
|
writeConcern | document |
|
collation | document |
collation: { locale: <string>, caseLevel: <boolean>, caseFirst: <string>, strength: <int>, numericOrdering: <boolean>, alternate: <string>, maxVariable: <string>, backwards: <boolean> }
|
hint | document |
|
|
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
并且没有文档与筛选器匹配,db.collectionre.placeOne()
将基于替换文档创建一个新文档。
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替换。
If a replacement operation changes the document size, the operation will fail.如果替换操作更改了文档大小,则操作将失败。
You cannot use the 不能对时间序列集合使用replaceOne()
method on a time series collection.replaceOne()
方法。
Starting in MongoDB 4.2, 从MongoDB 4.2开始,db.collection.replaceOne()
attempts to target a single shard, first by using the query filter. db.collection.replaceOne()
尝试首先使用查询筛选器以单个分片为目标。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.在早期版本中,操作尝试使用替换文档作为目标。
Starting in MongoDB 4.4, the replacement document does not need to include the shard key. 从MongoDB 4.4开始,替换文档不需要包含分片键。In MongoDB 4.2 and earlier, the replacement document must include the shard key.在MongoDB 4.2及更早版本中,替换文档必须包含分片键。
Starting in version 4.4, documents in sharded collections can be missing the shard key fields. 从4.4版开始,分片集合中的文档可能会缺少分片键字段。Take precaution to avoid accidentally removing the shard key when changing a document's shard key value.在更改文档的分片键值时,请采取预防措施,以避免意外删除分片键。
upsert
on a Sharded Collectionupsert
Starting in MongoDB 4.2, a 从MongoDB 4.2开始,在分片集合上包含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, starting in version 4.4, documents in a sharded collection can be missing the shard key fields. 但是,从4.4版开始,分片集合中的文档可能会缺少分片键字段。To target a document that is missing the shard key, you can use the 要将缺少shard键的文档作为目标,可以将null
equality match in conjunction with another filter condition (such as on the _id
field). null
相等匹配与另一个筛选条件(例如在_id
字段上)结合使用。For example:例如:
{ _id: <value>, <shardkeyfield>: null } // _id of the document missing shard key
Starting in MongoDB 4.2, you can update a document's shard key value unless the shard key field is the immutable 从MongoDB 4.2开始,您可以更新文档的分片键值,除非分片键值字段是不可变的_id
field. _id
字段。In MongoDB 4.2 and earlier, a document's shard key field value is immutable.在MongoDB 4.2及更早版本中,文档的shard键字段值是不可变的。
Starting in version 4.4, documents in sharded collections can be missing the shard key fields. 从4.4版开始,分片集合中的文档可能会缺少分片键字段。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()
修改现有的分片键值:
mongos
. mongos
上运行。Starting in version 4.4, documents in a sharded collection can be missing the shard key fields. 从4.4版开始,分片集合中的文档可能会缺少分片键字段。To use 要使用db.collection.replaceOne()
to set the document's missing shard key, you must run on a mongos
. db.collection.replaceOne()
设置文档缺少的分片键,必须在mongos
上运行。Do not issue the operation directly on the shard.不要直接对分片发出操作。
In addition, the following requirements also apply:此外,以下要求也适用:
null null |
|
null valuenull 值 |
|
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
相等匹配的一部分返回的,为了避免更新null
值键,请酌情包括其他查询条件(例如在_id
字段上)。
See also:另请参见:
db.collection.replaceOne()
can be used inside multi-document transactions.可以在多文档事务处理中使用。
In most cases, multi-document transaction incurs a greater performance cost over single document writes, and the availability of multi-document 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 multi-document transactions.也就是说,对于许多场景,适当地建模您的数据将最小化对多文档事务的需要。
For additional transactions usage considerations (such as runtime limit and oplog size limit), see also Production Considerations.有关其他事务使用注意事项(如运行时限制和oplog大小限制),请参阅生产注意事项。
Starting in MongoDB 4.4, you can create collections and indexes inside a multi-document transaction if the transaction is not a cross-shard write transaction.从MongoDB 4.4开始,如果事务不是跨分片写事务,则可以在多文档事务中创建集合和索引。
Specifically, in MongoDB 4.4 and greater, 具体来说,在MongoDB 4.4及更高版本中,带有db.collection.replaceOne()
with upsert: true
can be run on an existing collection or a non-existing collection. upsert:true
的db.collection.replaceOne()
可以在现有集合或不存在的集合上运行。If run on a non-existing collection, the operation creates the collection.如果在不存在的集合上运行,则该操作将创建集合。
In MongoDB 4.2 and earlier, the operation must be run on an existing collection.在MongoDB 4.2及更早版本中,操作必须在现有集合上运行。
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.要将写关注点用于事务,请参阅事务和写关注点。
The restaurant
collection contains the following documents:restaurant
集合包含以下文档:
{ "_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. upsert:true
将插入文档。See Replace with Upsert请参见使用Upsert替换
The restaurant
collection contains the following documents:restaurant
集合包含以下文档:
{ "_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
:upsert:true
将文档替换为name : "Pizza Rat's Pizzaria"
:
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. upsert:true
,文档将基于replacement
文档插入。The operation returns:操作返回:
{ "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 }
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 acknowledgement takes longer than the 如果确认时间超过wtimeout
limit, the following exception is thrown:wtimeout
限制,则会引发以下异常:
Changed in version 4.4.在版本4.4中更改。
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 | |
---|---|
clientSupplied | |
customDefault | setDefaultRWConcern .setDefaultRWConcern 。
|
getLastErrorDefaults | settings.getLastErrorDefaults field.settings.getLastErrorDefaults 字段。
|
implicitDefault |
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:myColl
集合包含以下文档:
{ _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:以下操作包括collation
选项:
db.myColl.replaceOne( { category: "cafe", status: "a" }, { category: "cafÉ", status: "Replaced" }, { collation: { locale: "fr", strength: 1 } } );
hint
for replaceOne
replaceOne
的hint
New in version 4.2.1.在版本4.2.1中新增。
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 }
:
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 } } ] )