[DOCS-15727] [Server] Investigate changes in SERVER-68847: Include "Query Framework" information in GetMore profiler entries Created: 08/Nov/22  Updated: 13/Nov/23  Resolved: 02/Feb/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 6.2.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Alison Huh
Resolution: Fixed Votes: 0
Labels: ready-for-work
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-68847 Include "Query Framework" information... Closed
Participants:
Days since reply: 1 year, 13 weeks, 1 day ago
Epic Link: DOCSP-22091

 Description   
Original Downstream Change Summary

Added the query framework as a field to profiler entries for GetMore commands.

Description of Linked Ticket

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.


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