-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2024-09-30, CAR Team 2024-10-14, CAR Team 2024-10-28, CAR Team 2024-11-11, CAR Team 2024-11-25, CAR Team 2024-12-23, CAR Team 2025-01-06, CAR Team 2025-01-20, CAR Team 2025-02-03, CAR Team 2025-02-17
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We have two cases (1, 2)in which the ShardServerOpObserver set the unsharded collection metadata. It is not clear to me which guarantees do we have in the opObserver around the fact that those collections are actually unsharded.
For instance in (1) do we really have the guarantee that we can't create a sharded temporary collection or that we will not create/shard the temporary collections after its creation?