[SERVER-30439] Fix dbCheck range checking Created: 31/Jul/17 Updated: 30/Oct/23 Resolved: 22/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.13 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Kuehne | Assignee: | Ian Kuehne |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Storage 2017-08-21, Storage 2017-09-11 |
| Participants: |
| Description |
|
We decided to change the meaning of the minKey and maxKey fields in the dbCheck invocation, so that the minimum is exclusive and the maximum inclusive instead of the other way around. Change that, both on the primary and in the oplog command. |
| Comments |
| Comment by Githook User [ 22/Aug/17 ] |
|
Author: {'username': 'ikuehne', 'email': 'ian.kuehne@mongodb.com', 'name': 'Ian Kuehne'}Message: Also includes fixes for |