[SERVER-82723] Refactor run_aggregate to use helper functions for executing the query Created: 02/Nov/23 Updated: 03/Nov/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Will Buerger | Assignee: | Backlog - Query Integration |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | quick-tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query Integration
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Execution of the query seems to be one logical step in the overall run_aggregate path. We should break it into a helper functions to clean up the high-level path, one for executing explain and one for executing a normal query. The inputs for explain are the aggregation plan, the explain verbosity, the executor, and the ReplyBuilderInterface. The inputs for normal execution are the aggregation plan, the expression context, the privilege vector, the externalDataSourceScopeGuard, the executors, and the ReplyBuilderInterface. |