-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Not Applicable
-
Storage Engines
-
8
Replace the "debug_mode" and "debug" features with control points. I haven't checked what action is needed. There are four types of these.
- Per connection: In "debug_mode" in both WiredTiger > Modules > WiredTiger API > wiredtiger_open and WiredTiger > Modules > WiredTiger API > WT_CONNECTION > reconfigure.
- Per session: In "debug" in per session in both WiredTiger > Modules > WiredTiger API > WT_CONNECTION > open_session and WiredTiger > Modules > WiredTiger API > WT_SESSION > reconfigure.
- Per checkpoint: In "debug" in WiredTiger > Modules > WiredTiger API > WT_SESSION > checkpoint.
- Per cursor: In "debug" in WiredTiger > Modules > WiredTiger API > WT_SESSION > open_cursor.
Per checkpoint and per cursor ones cannot be replaced with control points since we do not have either per checkpoint or per cursor control points.
Note, the control points implementation tickets are in three time periods:
- POC - Part of the POC.
- MVP - Part of the minimal viable product. However, even the POC can be used but less conveniently than the MVP.
- Future - Enhancements after the MVP.
The title of each ticket starts with the time period.
- depends on
-
WT-13580 MVP: Generate documentation for defined control points, not the framework
- Backlog