On this page本页内容
db.collection.insertMany()
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.
Inserts multiple documents into a collection.将多个文档插入到集合中。
The insertMany()
method has the following syntax:insertMany()
方法具有以下语法:
db.collection.insertMany( [ <document 1> , <document 2>, ... ], { writeConcern: <document>, ordered: <boolean> } )
document | document | |
writeConcern | document |
|
ordered | boolean | mongod instance should perform an ordered or unordered insert. mongod 实例应该执行有序插入还是无序插入。true .true 。 |
|
Given an array of documents, 给定一个文档数组,insertMany()
inserts each document in the array into the collection.insertMany()
将数组中的每个文档插入到集合中。
By default documents are inserted in order.默认情况下,文档按顺序插入。
If 如果ordered
is set to false, documents are inserted in an unordered format and may be reordered by mongod
to increase performance. ordered
设置为false
,则文档将以无序格式插入,并可能由mongod
重新排序以提高性能。Applications should not depend on ordering of inserts if using an unordered 如果使用无序insertMany()
.insertMany()
,则应用程序不应依赖于插入的顺序。
The number of operations in each group cannot exceed the value of the maxWriteBatchSize of the database. 每个组中的操作数不能超过数据库的maxWriteBatchSize
值。As of MongoDB 3.6, this value is 截至MongoDB 3.6,该值为100,000
. 100000
。This value is shown in the 此值显示在hello.maxWriteBatchSize
field.hello.maxWriteBatchSize
字段中。
This limit prevents issues with oversized error messages. 此限制可防止出现超大错误消息问题。If a group exceeds this limit, the client driver divides the group into smaller groups with counts less than or equal to the value of the limit. 如果某个组超过此限制,客户端驱动程序将该组划分为计数小于或等于限制值的较小组。For example, with the 例如,当maxWriteBatchSize
value of 100,000
, if the queue consists of 200,000
operations, the driver creates 2 groups, each with 100,000
operations.maxWriteBatchSize
值为100000
时,如果队列包含200000
个操作,则驱动程序将创建2个组,每个组包含100000
个操作。
The driver only divides the group into smaller groups when using the high-level API. 当使用高级API时,驱动程序仅将组划分为较小的组。If using db.runCommand() directly (for example, when writing a driver), MongoDB throws an error when attempting to execute a write batch which exceeds the limit.如果直接使用db.runCommand()(例如,在编写驱动程序时),MongoDB在尝试执行超出限制的写入批处理时会引发错误。
Starting in MongoDB 3.6, once the error report for a single batch grows too large, MongoDB truncates all remaining error messages to the empty string. 从MongoDB 3.6开始,一旦单个批次的错误报告变得太大,MongoDB会将所有剩余的错误消息截断为空字符串。Currently, begins once there are at least 2 error messages with total size greater than 当前,当至少有2条总大小大于1MB
.1MB
的错误消息时开始。
The sizes and grouping mechanics are internal performance details and are subject to change in future versions.尺寸和分组机制是内部性能细节,在未来版本中可能会更改。
Executing an 在分片集合上执行有序操作列表通常比执行无序列表慢,因为对于有序列表,每个操作都必须等待上一个操作完成。ordered
list of operations on a sharded collection will generally be slower than executing an unordered
list since with an ordered list, each operation must wait for the previous operation to finish.
If the collection does not exist, then 如果集合不存在,则insertMany()
creates the collection on successful write.insertMany()
在成功写入时创建集合。
_id
If the document does not specify an _id field, then 如果文档没有指定mongod
adds the _id
field and assign a unique ObjectId()
for the document. _id
字段,那么mongod
将添加_id
字段并为文档分配唯一的ObjectId()
。Most drivers create an ObjectId and insert the 大多数驱动程序创建一个_id
field, but the mongod
will create and populate the _id
if the driver or application does not.ObjectId
并插入_id
字段,但如果驱动程序或应用程序不创建并填充_id
,mongod
将创建并填充该_id
。
If the document contains an 如果文档包含_id
field, the _id
value must be unique within the collection to avoid duplicate key error._id
字段,则_id
值在集合中必须唯一,以避免重复键错误。
insertMany()
is not compatible with 与db.collection.explain()
.db.collection.explain()
不兼容。
Inserts throw a 插入引发BulkWriteError
exception.BulkWriteError
异常。
Excluding Write Concern errors, ordered operations stop after an error, while unordered operations continue to process any remaining write operations in the queue.不包括写入关注点错误,有序操作在错误后停止,而无序操作继续处理队列中的任何剩余写入操作。
Write concern errors are displayed in the 写入问题错误显示在writeConcernErrors
field, while all other errors are displayed in the writeErrors
field. writeConcernErrors
字段中,而所有其他错误显示在写入错误字段中。If an error is encountered, the number of successful write operations are displayed instead of a list of inserted _ids. 如果遇到错误,将显示成功的写入操作数,而不是插入的_id
列表。Ordered operations display the single error encountered while unordered operations display each error in an array.有序操作显示遇到的单个错误,而无序操作显示数组中的每个错误。
db.collection.insertMany()
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, if you specify an insert on a non-existing collection in a transaction, the collection is implicitly created.具体来说,在MongoDB 4.4及更高版本中,如果在事务中的不存在集合上指定插入,则会隐式创建集合。
In MongoDB 4.4 and earlier, the operation must be run on an existing collection.在MongoDB 4.4及更早版本中,操作必须在现有集合上运行。
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 following examples insert documents into the 以下示例将文档插入到products
collection.products
集合中。
_id
Field_id
字段The following example uses 以下示例使用db.collection.insertMany()
to insert documents that do not contain the _id
field:db.collection.insertMany()
插入不包含_id
字段的文档:
try { db.products.insertMany( [ { item: "card", qty: 15 }, { item: "envelope", qty: 20 }, { item: "stamps" , qty: 30 } ] ); } catch (e) { print (e); }
The operation returns the following document:该操作返回以下文档:
{ "acknowledged" : true, "insertedIds" : [ ObjectId("562a94d381cb9f1cd6eb0e1a"), ObjectId("562a94d381cb9f1cd6eb0e1b"), ObjectId("562a94d381cb9f1cd6eb0e1c") ] }
Because the documents did not include 由于文档不包含_id
, mongod
creates and adds the _id
field for each document and assigns it a unique ObjectId()
value._id
,mongod
为每个文档创建并添加_id
字段,并为其分配唯一的ObjectId()
值。
The ObjectId
values are specific to the machine and time when the operation is run. ObjectId
值特定于运行操作的机器和时间。As such, your values may differ from those in the example.因此,您的值可能与示例中的值不同。
_id
Field_id
字段的多个文档The following example/operation uses 下面的示例/操作使用insertMany()
to insert documents that include the _id
field. insertMany()
插入包含_id
字段的文档。The value of _id
must be unique within the collection to avoid a duplicate key error._id
的值在集合中必须是唯一的,以避免重复的键错误。
try { db.products.insertMany( [ { _id: 10, item: "large box", qty: 20 }, { _id: 11, item: "small box", qty: 55 }, { _id: 12, item: "medium box", qty: 30 } ] ); } catch (e) { print (e); }
The operation returns the following document:该操作返回以下文档:
{ "acknowledged" : true, "insertedIds" : [ 10, 11, 12 ] }
Inserting a duplicate value for any key that is part of a unique index, such as 为属于唯一索引(如_id
, throws an exception. _id
)的任何键插入重复值会引发异常。The following attempts to insert a document with a 以下操作尝试插入已存在_id
value that already exists:_id
值的文档:
try { db.products.insertMany( [ { _id: 13, item: "envelopes", qty: 60 }, { _id: 13, item: "stamps", qty: 110 }, { _id: 14, item: "packing tape", qty: 38 } ] ); } catch (e) { print (e); }
Since 由于_id: 13
already exists, the following exception is thrown:_id:13
已存在,将引发以下异常:
BulkWriteError({ "writeErrors" : [ { "index" : 0, "code" : 11000, "errmsg" : "E11000 duplicate key error collection: inventory.products index: _id_ dup key: { : 13.0 }", "op" : { "_id" : 13, "item" : "stamps", "qty" : 110 } } ], "writeConcernErrors" : [ ], "nInserted" : 1, "nUpserted" : 0, "nMatched" : 0, "nModified" : 0, "nRemoved" : 0, "upserted" : [ ] })
Note that one document was inserted: The first document of 请注意,插入了一个文档:_id: 13
will insert successfully, but the second insert will fail. _id:13
的第一个文档将成功插入,但第二个插入将失败。This will also stop additional documents left in the queue from being inserted.这也将阻止插入队列中剩余的其他文档。
With 如果ordered
to false
, the insert operation would continue with any remaining documents.ordered
为false
,插入操作将继续处理所有剩余文档。
The following attempts to insert multiple documents with 下面尝试插入多个带有_id
field and ordered: false
. _id
字段并且ordered: false
的文档。The array of documents contains two documents with duplicate 文档数组包含两个具有重复_id
fields._id
字段的文档。
try { db.products.insertMany( [ { _id: 10, item: "large box", qty: 20 }, { _id: 11, item: "small box", qty: 55 }, { _id: 11, item: "medium box", qty: 30 }, { _id: 12, item: "envelope", qty: 100}, { _id: 13, item: "stamps", qty: 125 }, { _id: 13, item: "tape", qty: 20}, { _id: 14, item: "bubble wrap", qty: 30} ], { ordered: false } ); } catch (e) { print (e); }
The operation throws the following exception:该操作引发以下异常:
BulkWriteError({ "writeErrors" : [ { "index" : 2, "code" : 11000, "errmsg" : "E11000 duplicate key error collection: inventory.products index: _id_ dup key: { : 11.0 }", "op" : { "_id" : 11, "item" : "medium box", "qty" : 30 } }, { "index" : 5, "code" : 11000, "errmsg" : "E11000 duplicate key error collection: inventory.products index: _id_ dup key: { : 13.0 }", "op" : { "_id" : 13, "item" : "tape", "qty" : 20 } } ], "writeConcernErrors" : [ ], "nInserted" : 5, "nUpserted" : 0, "nMatched" : 0, "nModified" : 0, "nRemoved" : 0, "upserted" : [ ] })
While the document with 由于重复的item: "medium box"
and item: "tape"
failed to insert due to duplicate _id
values, nInserted
shows that the remaining 5 documents were inserted._id
值,item: "medium box"
和item: "tape"
的文档无法插入,但nInserted
表示插入了其余5个文档。
Given a three member replica set, the following operation specifies a 给定一个三成员副本集,以下操作指定w
of majority
and wtimeout
of 100
:w
为majority
,wtimeout
为100
:
try { db.products.insertMany( [ { _id: 10, item: "large box", qty: 20 }, { _id: 11, item: "small box", qty: 55 }, { _id: 12, item: "medium box", qty: 30 } ], { w: "majority", wtimeout: 100 } ); } catch (e) { print (e); }
If the primary and at least one secondary acknowledge each write operation within 100 milliseconds, it returns:如果主服务器和至少一个辅助服务器在100毫秒内确认每个写入操作,则返回:
{ "acknowledged" : true, "insertedIds" : [ ObjectId("562a94d381cb9f1cd6eb0e1a"), ObjectId("562a94d381cb9f1cd6eb0e1b"), ObjectId("562a94d381cb9f1cd6eb0e1c") ] }
If the total time required for all required nodes in the replica set to acknowledge the write operation is greater than 如果副本集中所有所需节点确认写入操作所需的总时间大于wtimeout
, the following writeConcernError
is displayed when the wtimeout
period has passed.wtimeout
,则在wtimeout
时段结束后将显示以下writeConcernError
。
This operation returns:此操作返回:
WriteConcernError({ "code" : 64, "errmsg" : "waiting for replication timed out", "errInfo" : { "wtimeout" : true, "writeConcern" : { // Added in MongoDB 4.4 "w" : "majority", "wtimeout" : 100, "provenance" : "getLastErrorDefaults" } } })