[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.

> c.ensureIndex( { a:'2d' } )
> c.ensureIndex( { c:1, b:1 } ) // This index is necessary to trigger the described behavior.
> c.save( { a:[ 0, 0 ], b:1 } )
> c.find( { a:[ 0, 0 ], $or:[ { b:1 } ] } )



 Comments   
Comment by auto [ 06/Jun/12 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-5936 Remove unreachable MultiCursor::autoDedup() and check query optimizer cursor assumptions of its delegate cursors using verify.
Branch: master
https://github.com/mongodb/mongo/commit/a655e0e5968eea448ac5c2b2eed50c56e7500e6c

Comment by auto [ 06/Jun/12 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-5936 Prevent 'special' query plans from being used for a clause iterated $or query execution.
Branch: master
https://github.com/mongodb/mongo/commit/b2c99f16345d64b3f165d1338e484c3fcac5ff29

Comment by auto [ 06/Jun/12 ]

Author:

{u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

Message: SERVER-5936 Remove optional arguments to QueryPlanSet::make(), which were primarily use by unit tests.
Branch: master
https://github.com/mongodb/mongo/commit/cc8310563189736f6baf57f95102b0370eb8da2c

Generated at Thu Feb 08 03:10:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.