Loading...

XML

Word

Printable

JSON

Assigned Teams:

Query Integration
Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v8.0, v7.3, v7.0, v6.0, v5.0
Steps To Reproduce:
Hide

Create a collection with geo field "loc". Here's an example document to insert:

db.geo.insert({"loc" : { "type" : "Polygon", "coordinates" : [ [ [ 0, 0 ], [ 5, 0 ], [ 5, 5 ], [ 0, 5 ], [ 0, 0 ] ] ] } })

Create two indexes on the "loc" field, one of type "2dsphere" and one normal index:

db.geo.createIndex({loc: "2dsphere"}) db.geo.createIndex({loc: 1})

This sample query will hit this assertion error:

db.geo.find({loc: {$not: {$geoWithin: {$geometry: {type: "Polygon", coordinates: [[[-5,-5],[5,-5],[5,5],[-5,5],[-5,-5]]]}}}}})
Show
Create a collection with geo field "loc". Here's an example document to insert: db.geo.insert({ "loc" : { "type" : "Polygon" , "coordinates" : [ [ [ 0, 0 ], [ 5, 0 ], [ 5, 5 ], [ 0, 5 ], [ 0, 0 ] ] ] } }) Create two indexes on the "loc" field, one of type "2dsphere" and one normal index: db.geo.createIndex({loc: "2dsphere" }) db.geo.createIndex({loc: 1}) This sample query will hit this assertion error : db.geo.find({loc: {$not: {$geoWithin: {$geometry: {type: "Polygon" , coordinates: [[[-5,-5],[5,-5],[5,5],[-5,5],[-5,-5]]]}}}}})
Linked BF Score:
200

We manage to fail this assertion by trying to build geo bounds for a non-geo index. See steps to reproduce.

related to

SERVER-92427 QueryPlannerIXSelect::rateIndices has misleading behavior for $not queries that cannot use index negation

SERVER-98156 "Forward-port" changes to negated_geo_queries.js