[SERVER-1013] positional $ operator field mismatch Created: 13/Apr/10 Updated: 07/Dec/15 Resolved: 07/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Basic issue is that the matcher records a single array position in match details without any context. There is no validation that the field path of the matched array matches the field path leading to the positional operator.
|
| Comments |
| Comment by David Storch [ 07/Dec/15 ] |
|
This has come up in a few newer tickets: |
| Comment by Dwight Merriman [ 14/Sep/11 ] |
|
or always set $ to the matched pos of the first sub expression |
| Comment by Eliot Horowitz (Inactive) [ 19/Apr/11 ] |
|
We should probably just assert in this case. |