[SERVER-3793] geo index matching should handle certain multi key cases Created: 09/Sep/11 Updated: 10/Dec/14 Resolved: 18/Apr/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
It looks like geo uses a custom key generator, and it is not always equivalent to a single key index. In some cases we can't run matches like we would for a single key index. This is something I should have fixed as part of |
| Comments |
| Comment by Greg Studer [ 18/Apr/14 ] |
|
This issue should not longer apply given refactored index selection. Pinging hari.khalsa@10gen.com to verify. |
| Comment by auto [ 12/Sep/11 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |