[SERVER-17920] InternalError when using geoNear $meta projections with non-geo data Created: 07/Apr/15  Updated: 08/Apr/15  Resolved: 08/Apr/15

Status: Closed
Project: Core Server
Component/s: Geo, Querying
Affects Version/s: 3.1.1
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Kamran K. Assignee: Siyuan Zhou
Resolution: Done Votes: 0
Labels: 32qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-17929 Add full query support for $meta valu... Backlog
Operating System: ALL
Steps To Reproduce:

var t = db.geo_meta_projection;
t.drop();
 
t.insert({}); // ensure the namespace exists
 
t.find({}, {a: {$meta: 'geoNearDistance'}}).toArray();
t.find({}, {a: {$meta: 'geoNearPoint'}}).toArray();

Participants:

 Description   

The $meta projection operator supports two (undocumented) values for geo queries: geoNearDistance and geoNearPoint

These projection values trigger InternalErrors when used with non-geo data.

Versions affected: 2.6.0+

> t.find({}, {a: {$meta: 'geoNearDistance'}}).toArray();
2015-04-07T18:47:49.196-0400 E QUERY    Error: error: {
	"$err" : "Executor error: InternalError near loc dist requested but no data available",
	"code" : 17144
}
 
> t.find({}, {a: {$meta: 'geoNearPoint'}}).toArray();
2015-04-07T18:48:18.455-0400 E QUERY    Error: error: {
	"$err" : "Executor error: InternalError near loc proj requested but no data available",
	"code" : 17144
}


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