-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2024-04-15, CAR Team 2024-04-29
SERVER-80372 changed the implicit creation path by returning a CannotImplicitlyCreateCollection error to the router that - as a reaction - issues an explicit create command before retrying the write; this factually transformed any implicit creation in explicit creation + write.
The previous ticket left out implicit creations triggered by writes issued in retryable writes or transaction operations. This follow up ticket is aimed at following the new approach also in such cases, so that all creations coming from the router are going through the same path.
- depends on
-
SERVER-46971 Support createIndexes and createCollection inside transactions that explicitly specify readConcern
- Needs Scheduling
- is depended on by
-
SERVER-81937 Support creation of unsplittable collections in a transaction
- Open
-
SERVER-83875 Simplify flow for creating collection in a transaction on sharded clusters
- Blocked
-
SERVER-90897 Replace CollectionRouter with DbPrimaryRouter in cluster::createCollectionWithRouterLoop
- Blocked
- is duplicated by
-
SERVER-85366 Retryable Write should always register a collection in the sharding catalog
- Closed
- is related to
-
SERVER-80372 Make implicit collection creation call into `createCollection`
- Closed