-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Every failure in singleTableAccessPlans() is reported as failedToGetSingleTableAccessViaCBR by the executor. That includes:
- planning or CBR errors
- CBR accepting several plans it can't rank
- the single plan CBR can't estimate (
SERVER-138000)
SERVER-134637 will add another: falling back when a node's chosen plan uses a hashed, wildcard or collated index. These cases look the same in serverStatus and $queryStats.
Consider having singleTableAccessPlans() return a specific fallback reason, and add new reasons where needed, starting with the hashed/wildcard/collated index case.
- is duplicated by
-
SERVER-139099 Add a fallback metric for when JOO bails due to a hashed/wildcard/collated index
-
- Closed
-
- is related to
-
SERVER-138000 $setWindowFields with sortBy after a join-optimized $lookup+$unwind hits tassert
-
- Closed
-
-
SERVER-134637 CE of wildcard/hashed/collated index scans
-
- Closed
-
- related to
-
SERVER-139099 Add a fallback metric for when JOO bails due to a hashed/wildcard/collated index
-
- Closed
-