[SERVER-26038] Count and distinct operations do not include the shard filter stage Created: 09/Sep/16 Updated: 06/Dec/22 Resolved: 12/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.9, 3.3.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 2016-09-19 | ||||||||
| Participants: | |||||||||
| Description |
|
The count and distinct commands when run against a shard do not include the ShardFilterStage as part of their plan and because of this orphaned data does not get excluded. For the count command specifically, the shard filter stage can only be included when not using the "fast count" option, which uses the run time record counter. |