[SERVER-22630] $match should handle geo predicates in a consistent fashion Created: 16/Feb/16 Updated: 06/Dec/22 Resolved: 26/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benjamin Murphy | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | query-44-grooming | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
In document_source_match.cpp, "uassertNoDisallowedClauses" is used to validate the query passed into a $match stage. It confirms that $where, $near, and $nearSphere are not used inside the object, but does not check for $geoNear. It should either error in all cases, or allow geo predicates inside a $match. |
| Comments |
| Comment by David Storch [ 26/Jul/19 ] | ||||||||||||||
|
This refers to old code that no longer exists for DocumentSourceMatch. It appears that recent versions correctly reject $geoNear predicates in a $match:
Closing as Gone Away. |