[SERVER-85485] Fix legacy geo re-parsing for query stats. Created: 19/Jan/24 Updated: 02/Feb/24 Resolved: 23/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 8.0.0-rc0, 7.3.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Santiago Roche | Assignee: | Santiago Roche |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | flag-for-2885-backport | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v7.3
|
||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 45 | ||||||||||||
| Description |
|
BF-31401: Legacy geometry queries. Legacy geometry filters allow specifying a coordinate point as an embedded object, not specifying a type. The only constraint is that it must have two fields, and the first one is numeric, then it will be parsed in this manner.
"foo" is interpreted as the x-coordinate and "blah" as the y-coordinate. BF-31462: $nearSphere filter with embedded object, which does not specify a type.
The geo parser code, as mentioned in previous bugs, does not check the type of the implicit geometry embedded subobject, and always parses as a geoJSONPoint. |
| Comments |
| Comment by Githook User [ 02/Feb/24 ] |
|
Author: {'name': 'Santiago Roche', 'email': '69868136+sroches@users.noreply.github.com', 'username': 'sroches'}Message: GitOrigin-RevId: 8ed89c57231f4f9b52e47cc3ebeaaebcfa349a56 |
| Comment by Githook User [ 23/Jan/24 ] |
|
Author: {'name': 'Santiago Roche', 'email': '69868136+sroches@users.noreply.github.com', 'username': 'sroches'}Message: GitOrigin-RevId: 534c75036adda28e95c9d896bfc52ae978c7abb9 |
| Comment by Santiago Roche [ 23/Jan/24 ] |