-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Optimization
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Prior to SERVER-87466, replanning consisted of manually enumerating plans, constructing a MultiPlanStage, and running trials all within the CachedPlanStage. Post-SERVER-87466, we return a non-OK Status back to get_executor which begins normal query processing from the start, notably excluding the possibility of invoking subplanning. We should see if we can invoke subplanning in replanning - there is the possibility that we pick a better plan.
- related to
-
SERVER-87466 Trigger replanning by throwing an exception, instead of creating another planner
-
- Closed
-