shardCollection Event

A BSON object which serves as an identifier for the change stream event. This value is used as the resumeToken for the resumeAfter parameter when resuming a change stream. The _id object has the following form:

{
   "_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. See Resume Tokens for the full list of _data types.

For an example of resuming a change stream by resumeToken, see Resume a Change Stream.

The timestamp from the oplog entry associated with the event.

Change stream event notifications associated with a multi-document transaction all have the same clusterTime value: the time when the transaction was committed.

On sharded clusters, events with the same clusterTime may not all relate to the same transaction. 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.

UUID identifying the collection where the change occurred.

The identifier for the session associated with the transaction.

Only present if the operation is part of a multi-document transaction.

The namespace (database and or collection) affected by the event.

The name of the collection where the event occurred.

The name of the database where the event occurred.

Additional information on the change operation.

This document and its subfields only appears when the change stream uses expanded events.

Number of chunks created on each shard during a shardCollection operation.

Indicates whether the shard chunks were pre-split according to zones when the collection becamed sharded.

The shard key for the collection where the change occurred.

This has a value of true if the collection was sharded with a unique shard key.

The type of operation that the change notification reports.

Returns a value of shardCollection for these change events.

Together with the lsid, a number that helps uniquely identify a transction.

Only present if the operation is part of a multi-document transaction.

The 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.