refineCollectionShardKey Event
On this page
Summary
Description
Field | Type | Description | |||
---|---|---|---|---|---|
_id | Document | A BSON object which serves as an identifier for the
change stream event. This value is used as the
The For an example of resuming a change stream by | |||
clusterTime | Timestamp |
Due to oplog size limits,
multi-document transactions may create multiple
oplog entries. In a transaction, change stream events staged in a given oplog
entry share the same Events with the same To identify events for a single transaction, you can use the
combination of Changed in version 8.0. | |||
collectionUUID | UUID | UUID identifying the collection where the change occurred. New in version 6.0. | |||
ns | Document | The namespace (database and or collection) affected by the event. | |||
ns.coll | String | The name of the collection where the event occurred. | |||
ns.db | String | The name of the database where the event occurred. | |||
operationDescription | Document | Additional information on the change operation. This document and its subfields only appears when the change stream uses expanded events. New in version 6.0. | |||
operationDescription. shardKey | Document | The shard key for the collection where the change occurred. New in version 6.0. | |||
operationDescription. oldShardKey | Document | The shard key for the collection that changed. New in version 6.1. |
Example
The following example shows a refineCollectionShardKey
event:
{ "_id": { <ResumeToken> }, "operationType": "refineCollectionShardKey", "clusterTime": Timestamp({ t: 1654894852, i: 52 }), "collectionUUID": UUID("98046a1a-b649-4e5b-9c75-67594221ce19"), "ns": {"db": "reshard_collection_event", "coll": "coll"}, "operationDescription": { "shardKey": {"_id": 1, akey: 1}, "oldShardKey": {"_id": 1} } }