[SERVER-78996] Extend persistent query settings to support queryEngineVersion:"v3" Created: 14/Jul/23  Updated: 15/Jul/23  Resolved: 14/Jul/23

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

Type: Improvement Priority: Major - P3
Reporter: David Storch Assignee: Backlog - Query Optimization
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-77181 Implement query settings support in B... Open
Related
Assigned Teams:
Query Optimization
Participants:

 Description   

The persisted query settings project is introducing a way to persistently associate a query engine version with a query shape. It looks something like this:

db.adminCommand({
  setQuerySettings: <QueryInstance>
  settings: {queryEngineVersion: <version>}
});

The initial implementation will support "v1" (classic engine) and "v2" (SBE via the stage builders). The task for this ticket is to extend the persistent query settings feature so that it also supports "v3" – that is, full CQF with the Bonsai optimizer and SBE as the backend.

Ideally we would do this before shipping Bonsai. It may not be strictly required for CQF M2 since we will try to use Bonsai by default. Therefore, the more common use case for pinning a query shape to a queryEngineVersion will be to force classic or SBE via the stage builders if something goes wrong with Bonsai.



 Comments   
Comment by David Storch [ 14/Jul/23 ]

Closing as a duplicate of SERVER-77181.

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