[SERVER-78351] Limit pushdown doesn't work on sharded clusters if $skip stage is present Created: 22/Jun/23 Updated: 29/Oct/23 Resolved: 30/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 7.0.0-rc7, 6.0.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Evan Darke | Assignee: | Ted Tuckman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query Integration
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v7.0, v6.0
|
||||
| Participants: | |||||
| Description |
|
Summarized from https://mongodb.slack.com/archives/C039SULHYGH/p1684257620795129
Example 2: Sharded cluster, problem seems exacerbated by including a $project stage
Explain gist for query with {$skip:0} : https://gist.github.com/Edarke/c663b6f1acafa05af713781e4ce096eb
Explain gist for query without skip: https://gist.github.com/Edarke/5a423dc836a532d4b38228c421eac78c
|