[SERVER-24674] Bounds generation for collation-aware queries should check that array and object bounds actually contain nested strings Created: 20/Jun/16 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Hatch | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Participants: |
| Description |
|
Currently, as part of We should consider recursively exploring the bounds to determine if they do in fact contain a string. Currently we are excessively strict in requiring index collation to match query-collation on certain queries. This behavior also affects covering analysis. The CollationIndexKey class is responsible for key translation and determining whether a given element requires a collation-aware index key. |