[SERVER-44387] Consider allowing empty specification in aggregation projection Created: 04/Nov/19 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Anton Korshunov | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Optimization
|
| Participants: |
| Description |
|
Currently, we allow an empty projection specification in find()-style projections, which defaults to an exclusion projection, but we ban in it aggregation. As part of projection unification project we may want to lift this restriction and allow an empty projection specification in aggregation as well. That is, the following projection will become valid and will be treated as an exclusion projection with all fields included into the output document:
|