[SERVER-5336] explain() cursor field should store index used and type of scan in separate fields Created: 19/Mar/12  Updated: 10/Dec/14  Resolved: 14/Oct/14

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

Type: Improvement Priority: Minor - P4
Reporter: Kyle Banker Assignee: David Storch
Resolution: Duplicate Votes: 0
Labels: query_triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-10448 Revamp explain() formatting Closed
Participants:

 Description   

The cursor field for an explain() may look like this:

{ "cursor" : "BtreeCursor x_1 reverse multi" }

Rather than storing all of this information in the same field, we could break it up in to separate fields:

{ "cursor" : "BtreeCursor",
"index":

{x: 1}

,
"iterators": ["reverse", "multi"]
}

Not sure on the name of the last one, but you get the idea.



 Comments   
Comment by David Storch [ 14/Oct/14 ]

The new explain format introduced under SERVER-10448 provides richer introspection into the workings of the query optimizer and the query execution engine. The "cursor" field is no longer present in the new format. Closing as a duplicate.

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