[SERVER-82169] Consider not skipping first document when specifying minKey in dbCheck Created: 13/Oct/23 Updated: 14/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pm-855-milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
Currently, when running a data consistency or missing keys check with a minKey specified, we will skip the first document that refers to the minKey. This may be confusing for users, so we should consider not skipping that document. |