Docs Home → MongoDB Manual

createIndexes Event事件

On this page本页内容

Summary摘要

createIndexes

New in version 6.0. 6.0版新增。

A createIndexes event occurs when an index is created on the collection and the change stream has the showExpandedEvents option set to true.当在集合上创建索引并且更改流的showExpandedEvents选项设置为true时，将发生createIndexes事件。

Description描述

Field字段Type类型Description描述
_idDocumentA BSON object which serves as an identifier for the change stream event. BSON对象，用作更改流事件的标识符。This value is used as the resumeToken for the resumeAfter parameter when resuming a change stream. 恢复更改流时，此值用作resumeAfter参数的resumeToken。The _id object has the following form:_id对象具有以下形式： 
{
   "_data" : <BinData|hex string>
}
The _data type depends on the MongoDB versions and, in some cases, the feature compatibility version (fCV) at the time of the change stream's opening or resumption. _data类型取决于MongoDB版本，在某些情况下，还取决于更改流打开或恢复时的功能兼容性版本（fCV）。See Resume Tokens for the full list of _data types.请参阅恢复令牌以获取_data类型的完整列表。
For an example of resuming a change stream by resumeToken, see Resume a Change Stream. 有关通过resumeToken恢复更改流的示例，请参阅恢复更改流。
clusterTimeTimestampThe timestamp from the oplog entry associated with the event.与事件关联的oplog条目中的时间戳。
Change stream event notifications associated with a multi-document transaction all have the same clusterTime value: the time when the transaction was committed.与多文档事务关联的更改流事件通知都具有相同的clusterTime值：事务提交的时间。
On sharded clusters, events with the same clusterTime may not all relate to the same transaction. 在分片集群上，具有相同clusterTime的事件可能并不都与同一事务相关。Some events don't relate to a transaction at all.有些事件根本与事务无关。
To identify events for a single transaction, you can use the combination of lsid and txnNumber in the change stream event document. 要识别单个事务的事件，可以在变更流事件文档中使用lsid和txnNumber的组合。
New in version 4.0. 4.0版新增。
collectionUUIDUUIDUUID identifying the collection where the change occurred. 标识发生更改的集合。
New in version 6.0. 6.0版新增。
lsiddocumentThe identifier for the session associated with the transaction.与事务关联的会话的标识符。
Only present if the operation is part of a multi-document transaction. 仅当操作是多文档事务的一部分时才显示。
New in version 4.0. 4.0版新增。
nsdocumentThe namespace (database and or collection) affected by the event. 受事件影响的命名空间（数据库和/或集合）。
ns.dbstringThe name of the database where the event occurred. 发生事件的数据库的名称。
ns.collstringThe name of the collection where the event occurred. 发生事件的集合的名称。
operationDescriptiondocumentAdditional information on the change operation.有关更改操作的其他信息。
This document and its subfields only appears when the change stream uses expanded events. 只有当变更流使用展开的事件时，才会显示此文档及其子字段。
New in version 6.0. 6.0版新增。
operationDescription.
indexes		arrayAn array of documents listing the indexes that were created by the operation. 列出由操作创建的索引的文档数组。
New in version 6.0. 6.0版新增。
operationTypestringThe type of operation that the change notification reports.更改通知报告的操作类型。
Returns a value of createIndexes for these change events. 返回这些更改事件的createIndexes值。
txnNumberNumberLongTogether with the lsid, a number that helps uniquely identify a transction.与lsid一起，是一个有助于唯一识别事务的数字。
Only present if the operation is part of a multi-document transaction. 仅当操作是多文档事务的一部分时才显示。
New in version 4.0. 4.0版新增。
wallTimeISODateThe server date and time of the database operation. 数据库操作的服务器日期和时间。wallTime differs from clusterTime in that clusterTime is a timestamp taken from the oplog entry associated with the database operation event. wallTime与clusterTime的不同之处在于，clusterTime是从与数据库操作事件关联的oplog条目中获取的时间戳。
New in version 6.0. 6.0版新增。

Example实例

The following example shows a createIndexes event:以下示例显示了createIndexes事件：

{
   "_id": { <ResumeToken> },
   "operationType": "createIndexes",
   "clusterTime": Timestamp({ t: 1651257835, i: 1 }),
   "collectionUUID": UUID("06bced37-7cc8-4267-96aa-a58a422153d8"),
   "wallTime": ISODate("2022-04-29T18:43:55.160Z"),
   "ns": {
      "db": "test",
      "coll": "authors"
   },
   "operationDescription": {
      "indexes": [
         { "v": 2, "key": { "name": 1 }, "name": "name_1" }
      ]
   }
}