db.watch()

On this page本页内容

Definition定义

db.watch( pipeline, options )

For replica sets and sharded clusters only仅适用于副本集和分片群集

New in version 4.0.在版本4.0中新增 Requires featureCompatibilityVersion (fCV) set to "4.0" or greater. 需要将featureCompatibilityVersion(fCV)设置为"4.0"或更高。For more information on fCV, see setFeatureCompatibilityVersion.有关fCV的更多信息,请参阅setFeatureCompatibilityVersion

Opens a change stream cursor for a database to report on all its non-system collections.打开数据库的更改流游标以报告其所有非系统集合。

Parameter参数Type类型Description描述
pipelinearray

Optional. 可选。An Aggregation Pipeline consisting of one or more of the following aggregation stages:由以下一个或多个聚合阶段组成的聚合管道

Specify a pipeline to filter/modify the change events output.指定管道以筛选/修改更改事件输出。

Starting in MongoDB 4.2, change streams will throw an exception if the change stream aggregation pipeline modifies an event's _id field.从MongoDB 4.2开始,如果更改流聚合管道修改了事件的_id字段,则更改流将引发异常。

optionsdocumentOptional. 可选。Additional options that modify the behavior of db.watch().修改db.watch()行为的其他选项。

The options document can contain the following fields and values:options文档可以包含以下字段和值:

Field字段Type类型Description描述
resumeAfterdocument

Optional. 可选。Directs db.watch() to attempt resuming notifications starting after the operation specified in the resume token.指示db.watch()尝试在恢复令牌中指定的操作之后开始恢复通知。

Each change stream event document includes a resume token as the _id field. 每个变更流事件文档都包含一个恢复令牌作为_id字段。Pass the entire _id field of the change event document that represents the operation you want to resume after.传递更改事件文档的整个_id字段,该字段表示要在之后恢复的操作。

resumeAfter is mutually exclusive with startAfter and startAtOperationTime.resumeAfterstartAfterstartAtOperationTime相互排斥。

startAfterdocument

Optional. 可选。Directs db.watch() to attempt starting a new change stream after the operation specified in the resume token. 指示db.watch()在恢复令牌中指定的操作之后尝试启动新的更改流。Allows notifications to resume after an invalidate event.允许通知在无效事件后恢复。

Each change stream event document includes a resume token as the _id field. 每个变更流事件文档都包含一个恢复令牌作为_id字段。Pass the entire _id field of the change event document that represents the operation you want to resume after.传递更改事件文档的整个_id字段,该字段表示要在之后恢复的操作。

startAfter is mutually exclusive with resumeAfter and startAtOperationTime.startAfterresumeAfterstartAtOperationTime互斥。

New in version 4.2.在版本4.2中新增

fullDocumentstring

Optional. 可选。By default, db.watch() returns the delta of those fields modified by an update operation, instead of the entire updated document.默认情况下,db.watch()返回更新操作修改的字段的增量,而不是整个更新的文档。

Set fullDocument to "updateLookup" to direct db.watch() to look up the most current majority-committed version of the updated document. fullDocument设置为"updateLookup"以指示db.watch()查找更新文档的最新多数提交版本。db.watch() returns a fullDocument field with the document lookup in addition to the updateDescription delta.除了updateDescription delta之外,还返回一个包含文档查找的fullDocument字段。

batchSizeint

Optional. 可选。Specifies the maximum number of change events to return in each batch of the response from the MongoDB cluster.指定在MongoDB集群的每个批响应中返回的最大更改事件数。

Has the same functionality as cursor.batchSize().具有与cursor.batchSize()相同的功能。

maxAwaitTimeMSint

Optional. 可选。The maximum amount of time in milliseconds the server waits for new data changes to report to the change stream cursor before returning an empty batch.服务器在返回空批之前等待新数据更改报告给更改流游标的最长时间(毫秒)。

Defaults to 1000 milliseconds.默认为1000毫秒。

collationdocument

Optional. 可选。Pass a collation document to specify a collation for the change stream cursor.传递排序规则文档以指定更改流游标的排序规则

If omitted, defaults to simple binary comparison.如果省略,则默认为simple二进制比较。

startAtOperationTimeTimestamp

Optional. 可选。The starting point for the change stream. 变更流的起点。If the specified starting point is in the past, it must be in the time range of the oplog. 如果指定的起点在过去,则必须在oplog的时间范围内。To check the time range of the oplog, see rs.printReplicationInfo().要检查oplog的时间范围,请参阅rs.printReplicationInfo()

startAtOperationTime is mutually exclusive with resumeAfter and startAfter.startAtOperationTimeresumeAfterstartAfter相互排斥。

Returns:返回:A cursor over the change event documents. 游标在更改事件文档上。See Change Events for examples of change event documents.有关更改事件文档的示例,请参阅更改事件
Tip提示
See also: 参阅:

Availability可用性

Deployment部署

db.watch() is available for replica sets and sharded clusters:可用于副本集和分片群集:

  • For a replica set, you can issue db.watch() on any data-bearing member.对于副本集,可以对任何数据承载成员发出db.watch()
  • For a sharded cluster, you must issue db.watch() on a mongos instance.对于分片集群,必须在mongos实例上发出db.watch()

Storage Engine存储引擎

You can only use db.watch() with the Wired Tiger storage engine.您只能将db.watch()Wired Tiger存储引擎一起使用

Read Concern majority Support读取关注majority支持

Starting in MongoDB 4.2, change streams are available regardless of the "majority" read concern support; that is, read concern majority support can be either enabled (default) or disabled to use change streams.从MongoDB 4.2开始,无论"majority"读关注点支持如何,更改流都是可用的;也就是说,可以启用(默认)或禁用读取关注点majority支持以使用更改流

In MongoDB 4.0 and earlier, change streams are available only if "majority" read concern support is enabled (default).在MongoDB 4.0及更早版本中,只有启用了"majority"读取关注点支持(默认),更改流才可用。

Behavior行为

  • You cannot run db.watch() on the admin, local, or config database.不能在adminlocalconfig数据库上运行db.watch()
  • db.watch() only notifies on data changes that have persisted to a majority of data-bearing members.仅通知已持续到大多数数据承载成员的数据更改。
  • The change stream cursor remains open until one of the following occurs:更改流游标将保持打开状态,直到出现以下情况之一:
    • The cursor is explicitly closed.游标已明确关闭。
    • An invalidate event occurs; for example, a collection drop or rename.发生无效事件;例如集合删除或重命名。
    • The connection to the MongoDB deployment is closed.与MongoDB部署的连接已关闭。
    • If the deployment is a sharded cluster, a shard removal may cause an open change stream cursor to close, and the closed change stream cursor may not be fully resumable.如果部署是分片集群,分片移除可能会导致打开的变更流游标关闭,而关闭的变更流游标可能无法完全恢复。
  • You can run db.watch() for a database that does not exist. 您可以为不存在的数据库运行db.watch()However, once the database is created and you drop the database, the change stream cursor closes.但是,一旦创建了数据库并删除了数据库,变更流游标就会关闭。

Resumability可恢复性

Unlike the MongoDB Drivers, mongosh does not automatically attempt to resume a change stream cursor after an error. 与MongoDB驱动程序不同,mongosh不会在出错后自动尝试恢复更改流游标。The MongoDB drivers make one attempt to automatically resume a change stream cursor after certain errors.MongoDB驱动程序尝试在出现某些错误后自动恢复更改流游标。

db.watch() uses information stored in the oplog to produce the change event description and generate a resume token associated to that operation. 使用oplog中存储的信息来生成更改事件描述,并生成与该操作相关联的恢复令牌。If the operation identified by the resume token passed to the resumeAfter or startAfter option has already dropped off the oplog, db.watch() cannot resume the change stream.如果传递给resumeAfterstartAfter选项的resume令牌标识的操作已从oplog中删除,db.watch()将无法恢复更改流。

See Resume a Change Stream for more information on resuming a change stream.有关恢复更改流的详细信息,请参阅恢复更改流

Note注意
  • You cannot use resumeAfter to resume a change stream after an invalidate event (for example, a collection drop or rename) closes the stream. invalidate事件(例如,集合删除或重命名)关闭流后,不能使用resumeAfter恢复更改流。Starting in MongoDB 4.2, you can use startAfter to start a new change stream after an invalidate event.从MongoDB 4.2开始,您可以使用startAfter无效事件后启动新的更改流。
  • If the deployment is a sharded cluster, a shard removal may cause an open change stream cursor to close, and the closed change stream cursor may not be fully resumable.如果部署是分片集群,分片移除可能会导致打开的变更流游标关闭,而关闭的变更流游标可能无法完全恢复。
Note注意
Resume Token恢复令牌

The resume token _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/resumption (i.e. a change in fcv value does not affect the resume tokens for already opened change streams):恢复令牌_data类型取决于MongoDB版本,在某些情况下,取决于更改流打开/恢复时的功能兼容性版本(fcv)(即fcv值的更改不会影响已打开更改流的恢复令牌):

MongoDB VersionFeature Compatibility Version功能兼容性版本Resume Token _data Type恢复令牌_data类型
MongoDB 4.2 and later"4.2" or "4.0"Hex-encoded string (v1)十六进制编码字符串(v1
MongoDB 4.0.7 and later"4.0" or "3.6"Hex-encoded string (v1)十六进制编码字符串(v1
MongoDB 4.0.6 and earlier"4.0"Hex-encoded string (v0)十六进制编码字符串(v0
MongoDB 4.0.6 and earlier"3.6"BinData
MongoDB 3.6"3.6"BinData

Hex Encoded Tokens十六进制编码令牌

With hex-encoded string resume tokens, you can compare and sort the resume tokens.使用十六进制编码的字符串恢复令牌,可以对恢复令牌进行比较和排序。

Regardless of the fcv value, a 4.0 deployment can use either BinData resume tokens or hex string resume tokens to resume a change stream. 无论fcv值如何,4.0部署都可以使用BinData恢复令牌或十六进制字符串恢复令牌来恢复更改流。As such, a 4.0 deployment can use a resume token from a change stream opened on a collection from a 3.6 deployment.因此,4.0部署可以使用在3.6部署的集合上打开的更改流中的恢复令牌。

New resume token formats introduced in a MongoDB version cannot be consumed by earlier MongoDB versions.MongoDB版本中引入的新恢复令牌格式不能被早期的MongoDB使用。

Decode Resume Tokens解码恢复令牌

MongoDB provides a "snippet", an extension to mongosh, that decodes hex-encoded resume tokens.MongoDB提供了一个"snippet",它是mongosh的扩展,用于解码十六进制编码的恢复令牌。

You can install and run the resumetoken snippet from mongosh:您可以从mongosh安装并运行resumetoken代码段:

snippet install resumetoken
decodeResumeToken('<RESUME TOKEN>')

You can also run resumetoken from the command line (without using mongosh) if npm is installed on your system:如果系统上安装了npm,也可以从命令行运行resumetoken(不使用mongosh):

npx mongodb-resumetoken-decoder <RESUME TOKEN>

See the following for more details on:有关的详细信息,请参阅以下内容:

Full Document Lookup of Update Operations更新操作的完整文档查找

By default, the change stream cursor returns specific field changes/deltas for update operations. 默认情况下,更改流游标返回更新操作的特定字段更改/增量。You can also configure the change stream to look up and return the current majority-committed version of the changed document. 您还可以配置更改流以查找并返回更改文档的当前多数提交版本。Depending on other write operations that may have occurred between the update and the lookup, the returned document may differ significantly from the document at the time of the update.根据更新和查找之间可能发生的其他写入操作,返回的文档可能与更新时的文档有很大差异。

Depending on the number of changes applied during the update operation and the size of the full document, there is a risk that the size of the change event document for an update operation is greater than the 16MB BSON document limit. 根据更新操作期间应用的更改数量和完整文档的大小,更新操作的更改事件文档的大小可能大于16MB BSON文档限制。If this occurs, the server closes the change stream cursor and returns an error.如果发生这种情况,服务器将关闭更改流游标并返回错误。

Access Control访问控制

When running with access control, the user must have the find and changeStream privilege actions on the database resource. 使用访问控制运行时,用户必须对数据库资源具有findchangeStream权限操作。That is, a user must have a role that grants the following privilege:也就是说,用户必须具有授予以下权限角色

{ resource: { db: <dbname>, collection: "" }, actions: [ "find", "changeStream"] }

The built-in read role provides the appropriate privileges.内置read角色提供了适当的权限。

Example示例

The following operation in mongosh opens a change stream cursor on the hr database. mongosh中的以下操作将在hr数据库上打开一个变更流游标。The returned cursor reports on data changes to all the non-system collections in that database.返回的游标报告该数据库中所有非系统集合的数据更改。

watchCursor = db.getSiblingDB("hr").watch()

Iterate the cursor to check for new events. 循环游标以检查新事件。Use the cursor.isExhausted() method to ensure the loop only exits if the change stream cursor is closed and there are no objects remaining in the latest batch:使用cursor.isExhausted()方法确保循环仅在更改流游标关闭且最新批处理中没有剩余对象时退出:

while (!watchCursor.isExhausted()){
   if (watchCursor.hasNext()){
      printjson(watchCursor.next());
   }
}

For complete documentation on change stream output, see Change Events.有关变更流输出的完整文档,请参阅变更事件

←  db.version()Query Plan Cache Methods →