-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.2.4, 3.3.8
-
Component/s: None
-
Query Execution
-
ALL
-
-
(copied to CRM)
The database currently allows for partial indexes to be hinted regardless of the filters applied to the query. When these filters do not align with the partialFilterExpression for an index, there may be documents that match the query but are not included in the index. Forcing index usage via a hint in such a scenario will lead to the database returning incomplete results (a silent logical failure).
Returning an error is probably the most correct thing to do. Alternatively, the hint could be rejected and the standard plan generation process could be observed.
- is related to
-
SERVER-1599 support ability to pass hint to update
- Closed
- related to
-
SERVER-62362 Hints are allowed on special indexes like 2d and text but lead to incorrect results
- Open
-
SERVER-18449 Hinting sparse index without sparse-compatible predicate should be disallowed
- Backlog
-
SERVER-32540 Make partial index subset analysis consider $elemMatch object a subset of $exists
- Backlog
-
SERVER-26581 hinting index with different collation than query specifies should give an error or warning
- In Progress