[SERVER-51652] add better error handling for validate's use of KeyString Created: 15/Oct/20 Updated: 29/Oct/23 Resolved: 26/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, 4.4.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||
| Sprint: | Execution Team 2020-11-02 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
KeyString's functions can throw exceptions, but the validate command doesn't specifically catch these exceptions; instead, there is a top-level catch in validate that only reports the error and interrupts the rest of the validate procedure. It would be better if we could catch these exceptions at a lower level, thus allowing validate to skip over and continue after encountering index table records that aren't valid KeyStrings. |
| Comments |
| Comment by Githook User [ 30/Nov/20 ] |
|
Author: {'name': 'Eric Milkie', 'email': 'milkie@10gen.com', 'username': 'milkie'}Message: (cherry picked from commit ca65f33c3777678fda17164cc9e9da248469f409) |
| Comment by Githook User [ 26/Oct/20 ] |
|
Author: {'name': 'Eric Milkie', 'email': 'milkie@10gen.com', 'username': 'milkie'}Message: |