[SERVER-75505] Difference in dotted path handling between index types Created: 30/Mar/23 Updated: 12/May/23 Resolved: 12/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Will Buerger |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query Integration
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
If you have an index on {"my.field.name": 1}, then the document {"my.field.name": "a", "my": {"field": {"name": "b"}}, loc: [70, 40]} will produce an index key with value "b", as expected. However, if you have an index on {"loc": "2dsphere", "my.field.name": 1}, then it will index "a" (along with the encoded geo point). I'm not sure, but this may also hold true for other "special" index types that re-implement the logic to extract "normal" index keys for compound indexes. |
| Comments |
| Comment by Nicholas Zolnierz [ 13/Apr/23 ] |
|
Sending to QI as they own geo |