[DOCS-3785] Exact matches with 2d index no longer possible Created: 21/Jul/14 Updated: 16/Mar/15 Resolved: 04/Sep/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Thomas Rueckstiess | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 26 weeks ago | ||||||||
| Description |
|
The feature to use a 2d index for exact matches has been removed in a larger restructuring to clean up the geo framework. The docs still mention this feature: http://docs.mongodb.org/manual/tutorial/query-a-2d-index/#exact-matches-on-a-flat-surface This section needs to be removed or rewritten. Exact matches can be done with a regular index on {loc: 1} as a workaround. |
| Comments |
| Comment by Githook User [ 20/Aug/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |