Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
Query Optimization
Description
getExecutorDistinct() and getExecutorCount() have special performance-related transformations that they attempt to apply to each query solution tree returned from the query planner (both attempt to rewrite the query solution tree to contain DistinctNode or CountScan nodes instead of IndexScanNodes). These optimizations should instead be moved to the access planner; doing so will allow for unit testing of this logic.
Attachments
Issue Links
- related to
-
SERVER-45689 DISTINCT_SCAN candidate plans should be generated and evaluated with the multi-planner
-
- Backlog
-