-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Optimization
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Currently we have no build-time guarantee that the set of nodes that appear in ce_utils.cpp as supported vs. those handled by limit propagation/the cardinality estimator are identical.
This has resulted in SERVER-132567, and will likely remain a failure point as we expand the set of nodes supported by CBR.
This ticket is about finding a way to refactor this in such a away that we have a single source of truth on what set of nodes are supported by CBR and the various operations CBR might run on them (eg. cardinality estimation, costing, limit propagation etc.).
- is related to
-
SERVER-132567 Missing shard filter handling in propagateLimit results in tassert
-
- Closed
-