-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
-
Fully Compatible
-
ALL
-
v9.0
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Classic multiplanner obeys replanningData.shouldCache while the deferred multiplanner ignores it. "NeverCache" is passed when the replanned plan reaches a memory limit, so there's slightly different behavior there.
- is related to
-
SERVER-100786 maxTimeMs not respected for delay in query optimization
-
- Closed
-