In HELP-65363 MongoDB does a create-with-import in several steps. That is, they do a "dry-run" mode and then the "real" import:

• create with import=file_metadata=<string>
• perhaps session->alter the table's logging setting
• checkpoint (to write out the cleared write gens and timestamps from the import)
• drop with remove_files=false
• create with import=file_metadata=<string> (the "real" one)

Sometimes several checkpoints happen such that when they get to the second create the original metadata from the original export is no longer valid. So opening the root page from that metadata gives the file corruption error:

WiredTiger offers a import=(repair=true) configuration setting that finds the latest checkpoint in the table. MongoDB would like to use this only in the case where the 2nd create call above fails and hits the file corruption issue. The reason is that repair=true must read the entire table to find the latest checkpoint so it is only desired in the case where it is absolutely necessary. The vast majority of the time the second create-with-import succeeds.

This ticket is to add a configuration setting to import that signals to WiredTiger to not make the corruption error case fatal, and instead return an error to the caller.