[SERVER-80759] [CQF] Accept planFormat, properties, and phases parameters in queryPlannerDebug verbosity Created: 05/Sep/23  Updated: 25/Jan/24

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

Type: Task Priority: Major - P3
Reporter: Hana Pearlman Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-80542 [CQF] Implement explain for M2 based ... Open
is depended on by SERVER-80895 [CQF] Respect queryPlannerDebug param... Open
Related
related to SERVER-83121 [CQF] Introduce new queryPlannerDebug... Closed
Assigned Teams:
Query Optimization
Participants:

 Description   

Accept optional parameters to help reduce the output (add a way to output a string format for the ABTs, add a way to exclude properties, etc) according to the syntax document:

The extra parameters are optional and explicitly excluded from the stable API. They are meaningful only when the verbosity is set to queryPlannerDebug and result in an error if provided alongside other verbosities:

  • When internalIncludeProperties is false, the “properties” attached to each stage will be omitted.
  • When internalPlanFormat “string” is specified, the ABT under each optimizer phase will be represented in a stringified form.
  • When internalIncludePhases is specified, only the phases listed will be included in the output.

In this ticket we should consider how verbosity, internalCascadesOptimizerExplainVersion, and internalPlanFormat interact to determine the explain output. A relevant piece of code is here.


Generated at Thu Feb 08 06:44:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.