-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 8.0.0-rc0
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
0
The CollectionRoutingInfoTargeter always attempts to create the database, regardless of the operation type. This causes some issues, e.g. with listIndexes, where in sharded clusters a read operation incorrectly creates a database, instead of returning NamespaceNotFound.
- is related to
-
SERVER-98820 Make sure implicit database creation can only happen via CollectionRoutingInfoTargeter
- Backlog
- related to
-
SERVER-93179 Temporarily ignore DatabaseDifferCase from dbCheck
- Closed
-
SERVER-90517 mongos should authoritatively know whether a db exists or not
- Open