-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
ALL
-
-
CAR Team 2025-09-01, CAR Team 2025-09-15
-
🟥 DDL
-
None
-
None
-
None
-
None
-
None
-
None
Some compound wildcard indexes can be used as the shard key index, when this is not supported and can lead to severe correctness issues. We should add validation to prevent this.
In the repro attached, we see that when a collection is sharded and the shard key index has a wildcard component, documents can be missed in a full collection scan plan.
- is related to
-
SERVER-109929 shardCollection/reshardCollection must attempt to create a shardkey when a multikey/wildcard index exists on the shard key field
-
- Backlog
-
- related to
-
SERVER-89308 Create query property tester
-
- Closed
-
-
SERVER-109796 Investigate shardKeyIndex scan incorrect behavior with a compound wildcard index
-
- Needs Scheduling
-