[SERVER-42302] Move Document/Value library into the db/exec directory Created: 19/Jul/19 Updated: 29/Oct/23 Resolved: 01/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | David Storch |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2019-10-07 |
| Participants: |
| Description |
|
As part of consolidating the agg and find blocking sort implementations, we will begin using Document/Value throughout the query execution tree in both DocumentSources and PlanStages. Therefore, Document/Value will no longer be an aggregation framework-specific concept. The code should move out of db/pipeline, which houses the code for the aggregation framework, and into db/exec, which houses the query execution engine. |
| Comments |
| Comment by Githook User [ 01/Oct/19 ] |
|
Author: {'name': 'David Storch', 'username': 'dstorch', 'email': 'david.storch@mongodb.com'}Message: Document/Value is now used throughout the query execution |
| Comment by Githook User [ 01/Oct/19 ] |
|
Author: {'name': 'David Storch', 'username': 'dstorch', 'email': 'david.storch@mongodb.com'}Message: |