-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Security Level: Public (Available to anyone on the web)
-
Storage Engines, Storage Engines - Persistence
-
1,966.563
-
SE Persistence backlog
-
None
Issue Summary
In the bt_vrfy.c file, the current code checks if the file name matches WT_METAFILE_URI to skip the history store explicit call during verification. The question was raised whether this check should be updated to use WT_IS_URI_METADATA to ensure both asc and dsc are covered.
Context
The relevant code snippet is:
skip_hs = strcmp(name, WT_METAFILE_URI) == 0 || WT_IS_URI_HS(name) || F_ISSET(session, WT_SESSION_DEBUG_DO_NOT_CLEAR_TXN_ID);
Currently, this only matches WT_METAFILE_URI. However, there may be multiple forms of metadata URIs (such as asc and dsc variants) that should also be included in this check. The macro WT_IS_URI_METADATA would cover all metadata URIs, ensuring the verification logic is consistent and comprehensive.
Proposed Solution
Update the check from strcmp(name, WT_METAFILE_URI) == 0 to WT_IS_URI_METADATA(name) in bt_vrfy.c to ensure all metadata URIs are properly handled during verification.
Original Slack thread: https://mongodb.slack.com/archives/C0AKD3HPD8T/p1775715010482329
This ticket was generated by AI from a Slack thread.
- is related to
-
WT-17940 Investigate verifying WT_DISAGG_METADATA_URI (shared metadata) during verify
-
- Open
-