[SERVER-51625] Ensure that API version fields are propagated to sub-operations in aggregate command. Created: 15/Oct/20 Updated: 06/Dec/22 Resolved: 05/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Arun Banala | Assignee: | Backlog - Query Optimization |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Participants: | |||||||||
| Description |
|
We will have to attach APIVersion fields (version, apiStrict and apiDeprectedErrors) to the DBDirectClient. We need to validate this for $unionWith and $lookUp, both on sharded and non-sharded clusters. |