Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-78996

Extend persistent query settings to support queryEngineVersion:"v3"

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization

      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.

            Assignee:
            backlog-query-optimization [DO NOT USE] Backlog - Query Optimization
            Reporter:
            david.storch@mongodb.com David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: