On this page本页内容
Starting in version 3.2, MongoDB also provides the 从3.2版开始,MongoDB还提供了db.collection.bulkWrite()
method for performing bulk write operations.db.collection.bulkWrite()
方法来执行批量写入操作。
Bulk()
Bulk operations builder used to construct a list of write operations to perform in bulk for a single collection. 批量操作生成器用于构造要为单个集合批量执行的写入操作列表。To instantiate the builder, use either the 要实例化生成器,请使用db.collection.initializeOrderedBulkOp()
or the db.collection.initializeUnorderedBulkOp()
method.db.collection.initializeOrderedBulkOp()
或db.collection.initializeUnorderedBulkOp()
方法。
The builder can construct the list of operations as ordered or unordered.生成器可以按有序或无序构造操作列表。
With an ordered operations list, MongoDB executes the write operations in the list serially. 在有序操作列表中,MongoDB串行执行列表中的写入操作。If an error occurs during the processing of one of the write operations, MongoDB will return without processing any remaining write operations in the list.如果在处理其中一个写入操作期间发生错误,MongoDB将返回,而不处理列表中的任何剩余写入操作。
Use 使用db.collection.initializeOrderedBulkOp()
to create a builder for an ordered list of write commands.db.collection.initializeOrderedBulkOp()
为写入命令的有序列表创建生成器。
When executing an 当执行有序的操作列表时,MongoDB根据操作类型和连续性对操作进行分组;即,将相同类型的连续操作分组在一起。ordered
list of operations, MongoDB groups the operations by the operation type
and contiguity; i.e. contiguous operations of the same type are grouped together. For example, if an ordered list has two insert operations followed by an update operation followed by another insert operation, MongoDB groups the operations into three separate groups: first group contains the two insert operations, second group contains the update operation, and the third group contains the last insert operation. 例如,如果一个有序列表有两个插入操作,随后是一个更新操作,然后是另一个插入操作。MongoDB将这些操作分为三个单独的组:第一组包含两个插入作业,第二组包含更新作业,第三组包含最后一个插入作业。This behavior is subject to change in future versions.此行为可能会在将来的版本中更改。
Bulk()
operations in mongosh
and comparable methods in the drivers do not have a limit for the number of operations in a group. mongosh
中的Bulk()
操作和驱动程序中的类似方法对组中的操作数量没有限制。To see how the operations are grouped for bulk operation execution, call 要查看操作如何分组以执行批量操作,请在执行后调用Bulk.getOperations()
after the execution.Bulk.getOperations()
。
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.
With an unordered operations list, MongoDB can execute in parallel, as well as in a nondeterministic order, the write operations in the list. If an error occurs during the processing of one of the write operations, MongoDB will continue to process remaining write operations in the list.使用无序操作列表,MongoDB可以并行执行列表中的写入操作,也可以以不确定的顺序执行。如果在处理其中一个写入操作期间发生错误,MongoDB将继续处理列表中剩余的写入操作。
Use 使用db.collection.initializeUnorderedBulkOp()
to create a builder for an unordered list of write commands.db.collection.initializeUnorderedBulkOp()
为写命令的无序列表创建生成器。
When executing an 在执行无序操作列表时,MongoDB会对操作进行分组。unordered
list of operations, MongoDB groups the operations. With an unordered bulk operation, the operations in the list may be reordered to increase performance. 对于无序批量操作,可以对列表中的操作重新排序以提高性能。As such, applications should not depend on the ordering when performing 因此,应用程序在执行无序批量操作时不应依赖于顺序。unordered
bulk operations.
Bulk()
operations in mongosh
and comparable methods in the drivers do not have a limit for the number of operations in a group. mongosh
中的Bulk()
操作和驱动程序中的类似方法对组中的操作数量没有限制。To see how the operations are grouped for bulk operation execution, call 要查看操作如何分组以执行批量操作,请在执行后调用Bulk.getOperations()
after the execution.Bulk.getOperations()
。
<Bulk()
can be used inside multi-document transactions.Bulk()
可以在多文档事务中使用。
For 对于Bulk.insert()
operations, the collection must already exist.Bulk.insert()
操作,集合必须已经存在。
For 对于Bulk.find.upsert()
, if the operation results in an upsert, the collection must already exist.Bulk.find.upsert()
,如果操作导致upsert,则集合必须已经存在。
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.要将写关注点用于事务,请参阅事务和写关注点。
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大小限制),请参阅生产注意事项。
The Bulk()
builder has the following methods:Bulk()
生成器有以下方法:
Bulk.insert() | |
Bulk.find() | |
Bulk.find.removeOne() | |
Bulk.find.remove() | |
Bulk.find.replaceOne() | |
Bulk.find.updateOne() | |
Bulk.find.update() | multi update operation to a list of operations.multi 更新操作添加到操作列表中。 |
Bulk.find.upsert() | upsert: true for an update operation.upsert:true 。 |
Bulk.execute() | |
Bulk.getOperations() | Bulk() operations object.Bulk() 操作对象中执行的写入操作数组。 |
Bulk.tojson() | Bulk() operations object.Bulk() 操作对象中的操作数和批处理数。 |
Bulk.toString() | Bulk.tojson() results as a string.Bulk.tojson() 结果。 |