Currently, the wt command-line utility doesn’t work with DisAgg tables because it doesn’t know how to load PALS(I). For PALM, this could be easily addressed by extending the -C configuration string to include all the necessary DisAgg arguments. However, it’s unclear what process could be used for PALI.

The wt verify utility itself also requires some adjustments to handle layered: tables, but the core functionality (which effectively just calls session->verify()) should work fine for verifying DisAgg tables.

That said, it’s unclear how support for PALI could be implemented, and adding support for PALM would likely be beneficial only for internal testing. The current wt verify tests mainly focus on validating the ability to detect corruptions, but the method of corrupting tables used in those tests cannot be reused for DisAgg. This means new corruption detection tests would need to be written, which could likely be done without using the command-line utility. As a result, there is currently no clear reason to support wt verify for DisAgg tables.

However, I've decided to create this ticket to not forget to discuss this question from the global perspective of shipping the WT command line tools with Mongo. That could be a part of the bigger question for understanding whether we need to support the whole toolset for DisAgg.