-
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
Three potential places where path arrayness is used in the codebase that we can refactor to use the new API:
- planner_ixselect.cpp - QueryPlannerIXSelect::notEqualsNullCanUseIndex()
- distinct_access.cpp - isAnyComponentOfPathOrProjectionMultikey()
- cardinality_estimator.cpp - CardinalityEstimator::CardinalityEstimator()
For each, let's validate that the arrayness API would be beneficial and perform the refactor.
1.
|
Refactor cardinality estimator to use the ArraynessAPI | SERVER-114173 |
|
In Code Review | Matt Olma | |
2.
|
Refactor distinct access to use the ArraynessAPI | SERVER-114175 |
|
In Code Review | Matt Olma |