-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
QO 2022-10-31, QO 2022-11-14
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently the profiler includes the `queryExecutionEngine` field (SERVER-62760 will rename this field to `queryFramework`) in its log entries. This information is not attached to subsequent GetMore commands executed on the same cursor. This is because we attach the query framework (classic, sbe, or cqf) information to the CurOp object in OpCtx, where GetMore commands have their own OpCtx.
Perhaps this information is already available in the ClientCursor which holds a reference to the original command's opCtx. Another potential way to implement this functionality would be to define a virtual function to PlanExecutor which returns the queryFramework.
- is depended on by
-
COMPASS-6282 Investigate changes in SERVER-68847: Include "Query Framework" information in GetMore profiler entries
-
- Closed
-
-
-
- Closed
-
- is related to
-
SERVER-71172 Expose hybrid plans in profiler, slow query log, and currentOp output
-
- Closed
-
- related to
-
SERVER-68803 Add whether SBE is in use to currentOp output
-
- Closed
-