-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Querying
-
Query Optimization
Looks like it's possible to hint an index that has one collation defined but specify a different collation on the query itself.
It should probably be an error, similar to requests in SERVER-8564 but I can also see this being a warning, since it's possible to conceive a query that is using default collation but wants to use an existing different collation index for filtering in a scenario where this does not impact the results.
- is 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-26413 Hinting an incompatible partial index can return incomplete results
- Backlog
-
SERVER-89744 Resharding incorrectly builds {locale: "simple"} secondary indexes with collection's non-"simple" default collation
- Closed