[SERVER-22460] Logic for applying distinct scan and count scan optimizations should be moved to data access planner Created: 03/Feb/16 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Participants: | |||||||||
| 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. |