[SERVER-25899] Make the distinct command always execute as an aggregation pipeline Created: 31/Aug/16 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 4 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
We execute distinct over views as aggregations, but there is no reason that all distinct commands couldn't internally use the agg path. As part of this work, we need to allow the aggregation system to make use of the DISTINCT_SCAN fast path for aggregations that are logically distinct operations. |
| Comments |
| Comment by David Golden [ 11/Nov/16 ] |
|
Please consider addressing |
| Comment by Andy Schwerin [ 31/Aug/16 ] |
|
If you do this, please do it to mongos as well. |