[SERVER-37140] Investigate what other StageConstraints are "inheritable" Created: 14/Sep/18 Updated: 06/Dec/22 Resolved: 05/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Participants: | |||||||||
| Description |
|
In This ticket is to investigate what other StageConstraints should be inherited, if any. If there are more, we can genericize StageConstraints::resolveDiskUseAndTransactionRequirement() |
| Comments |
| Comment by David Storch [ 05/Oct/18 ] |
|
Closing per Charlie's comment above. |
| Comment by Charlie Swanson [ 24/Sep/18 ] |
|
The code review for The other constraints are: StreamType (streaming or blocking), Position Requirement (first, last, or none), HostTypeRequirement (5 choices), and ChangeStreamRequirement (whitelist, blacklist, or 'is a change stream stage'). None of those really make sense to 'roll up' to me either, so I'd recommend closing this. david.storch agreed? |
| Comment by David Storch [ 21/Sep/18 ] |
|
charlie.swanson to elaborate on the potential impact of the constraints implementation as it exists today. |