-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: Query Execution
-
Query Execution
-
Fully Compatible
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The Compass team is working on COMPASS-7794 and ran into some challenges processing the explain output of express plans. In particular, the keyPattern field has a different format for express plans that is proving difficult to parse. For express plans, we see the following output:
{
"stage" : "EXPRESS_IXSCAN",
"keyPattern" : "{ _id: 1 }",
...
},
and
{
"stage" : "EXPRESS_IXSCAN",
"keyPattern" : "{ a: 1 }",
...
},
whereas regular index scans result in the following:
"stage" : "IXSCAN", "keyPattern" : { "a" : 1 },
The ask is to make the keyPattern field more easily parseable, either by wrapping the field names in quotes:
"keyPattern": "{ \"a\": 1 }",
or by serializing the pattern as an object as we do in non-express explain output.
- is depended on by
-
COMPASS-10806 Investigate changes in SERVER-92981: Make the keyPattern field in express plan explains more easily parseable
-
- Needs Triage
-
- related to
-
COMPASS-7794 Investigate changes in SERVER-87529: Consider adding index used to plan summary for express path
-
- Closed
-