-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 8.1.0-rc0, 8.0.0-rc10
-
Component/s: None
-
Catalog and Routing
-
ALL
-
-
CAR Team 2024-05-27, CAR Team 2024-06-10, CAR Team 2024-06-24
-
200
When an unsharded time-series collection was created but only with the buckets collection (this could be due to a stepdown before creating the view + a concurrent view creation on the same namespace), creating and sharding another regular collection with the same namespace will create the shard key index on the buckets collection.
Despite the unclear expected behavior when a dangling buckets collection exists in sharding, this should still be considered problematic since the now sharded collection is missing the shard key index. This fails the metadata check.
- is fixed by
-
SERVER-90862 Creating a collection or a view should fail if a bucket namespace exists without its view
- Backlog