[SERVER-5936] assertion (fassert) may be triggered by exact match geo lookup with $or Created: 25/May/12 Updated: 11/Jul/16 Resolved: 07/Jun/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo, Querying |
| Affects Version/s: | None |
| Fix Version/s: | 2.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Geo operators are prevented inside top level $or clauses, and the $or implementation is not used when they are present outside $or clauses. However, it is possible for an exact match location query used with $or to trigger a code path disallowed for geo cursors which currently causes an fassert.
|
| Comments |
| Comment by auto [ 06/Jun/12 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |
| Comment by auto [ 06/Jun/12 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |
| Comment by auto [ 06/Jun/12 ] |
|
Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}Message: |