[SERVER-20261] Planner unable to find index for $geoNear query with readConcern majority Created: 02/Sep/15 Updated: 23/Feb/18 Resolved: 02/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 3.1.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Michael Grundy | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | jstest attached |
||||||||||||
| Participants: | |||||||||||||
| Description |
|
Running a $geoNear on a 2d index with a readConcern majority will fail with the following error:
|
| Comments |
| Comment by Michael Grundy [ 02/Sep/15 ] |
|
Duplicate of |
| Comment by Michael Grundy [ 02/Sep/15 ] |
|
Still fails with w:majority on the index build. |
| Comment by Eric Milkie [ 02/Sep/15 ] |
|
Ah, for this one you must pair read level majority reads with w:majority writes. In this case, I think it will fix the test if you do w:majority on the index build. |