[DOCS-3372] Note Invalid geoNear Queries with more than one near predicate Created: 08/May/14 Updated: 07/Jul/14 Resolved: 07/Jul/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 32 weeks, 2 days ago |
| Description |
|
For example, the server now correctly complains when you have more than one near predicate when calling geoNear. |
| Comments |
| Comment by Githook User [ 07/Jul/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Sam Kleinman (Inactive) [ 01/Jul/14 ] |
|
Let's morph this ticket to address only the geoNear issue, and we can address additional rejected queries as part of separate tickets |
| Comment by Randolph Tan [ 08/May/14 ] |
|
This came about from cs-12185 |