-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-03-17
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
The execution of the moveCollection and unshardCollection user-commands is backed by the ReshardingCoordinator, who triggers the emission of a reshardCollection op entry from the primary shard of the targeted namespace when a request is committed.
Different consumers of such an op entry may be interested in accepting/discarding it depending on the type of user request that originated it: in order to support this, the content of the op entry should include information about its provenance.