[SERVER-22473] Parsing invalid geo match predicate should not generate exception Created: 04/Feb/16 Updated: 25/May/21 Resolved: 30/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo, Querying |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Joshua Lapacik (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng, query-44-grooming | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Query Optimization 2021-04-05 | ||||||||
| Participants: | |||||||||
| Description |
|
The return type of MatchExpressionParser::parse() is StatusWith<std::unique_ptr<MatchExpression>>, but a UserException is thrown from this method when given an invalid geo near predicate (see GeoNearExpression::parseLegacyQuery(), GeoNearExpression::parseNewQuery(), and GeoNearExpression::parseFrom()). Instead, an error Status should be returned. |
| Comments |
| Comment by Githook User [ 30/Mar/21 ] |
|
Author: {'name': 'joshua', 'email': '80741223+jlap199@users.noreply.github.com', 'username': 'jlap199'}Message: |
| Comment by Joshua Lapacik (Inactive) [ 25/Mar/21 ] |
|
rassi can you give an example of an invalid predicate that throws this exception? |