-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
v8.0
-
CAR Team 2024-05-13, CAR Team 2024-05-27, CAR Team 2024-06-10, CAR Team 2024-06-24, CAR Team 2024-07-08, CAR Team 2024-07-22, CAR Team 2024-08-05, CAR Team 2024-08-19, CAR Team 2024-09-02, CAR Team 2024-09-16
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
While serving a moveCollection request, the namespace to migrate gets tentatively registered on the sharding catalog.
Purpose of this ticket is to improve test coverage in order to make sure that:
All type of collections that can be tracked/moved are properly registered on the sharding catalog(already done underSERVER-88286)- The state of the sharding catalog does not change when moveCollection is invoked on namespaces that can't be tracked/moved (e.g. system collections, views, fle state collections)