[SERVER-82720] Refactor run_aggregate to use a helper function that manages lock acquisition and collation resolution 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 |
|
Lock acquisition and collation resolution seems to be one large logical step on the run_aggregate path. We should break it into a helper function to clean up the high-level path. This step should just require the AggregationPlan as input, and should output the collation. Preparation for change streams (setting the execution namespace and other checks) as well as lock acquisition happens alongside. |