[SERVER-4213] explain doesn't include index name on geo queries Created: 04/Nov/11 Updated: 11/Jul/16 Resolved: 18/Apr/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Geo, Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 3 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
> db.system.indexes.find() , "ns" : "test.system.users", "name" : "id" } , "ns" : "test.foo", "name" : "id" } , "ns" : "test.foo", "name" : "a_1_b_1" } , "ns" : "test.foo", "name" : "b_1" } , "ns" : "test.foo", "name" : "l__a_1" } , "ns" : "test.foo", "name" : "l__b_2" } > db.foo.find({l:{$near:[55,55]},b:1}).explain() } Note that it just says "GeoSearchCursor", without the name of the cursor. Unlike a query on a normal btree cursor, which includes the cursor name as well as the type: > db.foo.find( {a:1}).explain() , { "$maxElement" : 1 } ] |
| Comments |
| Comment by Greg Studer [ 18/Apr/14 ] |
|
This is a non-issue with other explain changes. Attaching hari.khalsa@10gen.com for notification but no action needed. |