-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
I believe this is only used when eMRC=off. So we should be able to remove that from the storage engine API's surface area as well as the underlying call into WT.
- has to be done before
-
WT-9172 remove force configuration for WT_CONNECTION.set_timestamp API
-
- Blocked
-