-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Diagnostics
-
None
-
Fully Compatible
-
v4.4
-
Execution Team 2020-11-02
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.
- related to
-
WT-6538 Fix onpage prepare visibility check if the start and stop are from the same prepared transaction
- Closed