Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Critical - P2
Fix Version/s: 9.0.0-rc1
Affects Version/s: None
Component/s: None
Labels:
- controlables

Assigned Teams:

Query Optimization
Backwards Compatibility:
Fully Compatible
Linked BF Score:
200
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

We currently have a feature flag used to disable usage of CBR, reverting to planning a query using only multiplanning. Once the feature flag is removed (potentially around 9.1 timeframe), we longer have a way to plan using only multiplanning. This is important to address any stability issues that arise around CBR and for analyzing planning issues.

is duplicated by

SERVER-127562 Create a server parameter to controll if CBR or MP is being used

Closed

related to

SERVER-131325 Fix query golden output directory for multiPlanning

Closed

SERVER-132020 Index choice regression when using pure CBR

Closed

SERVER-129762 Complete TODO listed in SERVER-118487

Closed

SERVER-118487 Re-enable histogram CBR fallback in plan cache test

Closed

SERVER-131947 Use default value for internalQueryPlanRanker in JOO suites

Closed

(1 related to)

Assignee:: Milena Ivanova
Reporter:: Jess Balint
Participants:: Githook User, Jess Balint, Milena Ivanova
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Feb 13 2026 05:28:28 PM UTC
Updated:: Jul 22 2026 04:48:43 PM UTC
Resolved:: Jul 14 2026 09:00:49 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty