[SERVER-42771] Add new constructor to build ExpressionContext without input BSON Created: 12/Aug/19 Updated: 29/Oct/23 Resolved: 16/Aug/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: | Jacob Evans | Assignee: | Jacob Evans |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Query 2019-08-26 | ||||||||
| Participants: | |||||||||
| Description |
|
AggregationRequest is given BSONObj containing the input query for safekeeping. We need to be able to build an ExpressionContext and we cannot provide this BSONObj since we're building the pipeline in-place. So we need to build a new entry point to ExpressionContext that does not depend on AggregationRequest. |
| Comments |
| Comment by Githook User [ 16/Aug/19 ] |
|
Author: {'name': 'Jacob Evans', 'email': 'jacob.evans@10gen.com'}Message: |
| Comment by Jacob Evans [ 14/Aug/19 ] |
|
No, it's correct now, it used to be "Decouple AggregationRequest from input BSON" which was stale. |
| Comment by Charlie Swanson [ 14/Aug/19 ] |
|
jacob.evans is the description/title now stale here? |