Cairo load restoration consistency during parallelized constraint evaluation

Using the cairo load utility to restore logical backups generated via cairo dump requires a clean target environment to prevent schema collision conflicts. While the process successfully captures point-in-time snapshots of data structures, the behavior remains inconsistent during parallelized imports when complex nested constraints are active.

Because the standard load utility lacks a native 'verify-only' mode, users must rely on external checksum scripts or row-count comparisons to ensure data integrity. There is uncertainty regarding whether the engine handles transient state failures correctly when constraints are not explicitly disabled prior to the import process.

How does Cairo manage transient state failures when nested constraints are evaluated during a parallelized cairo load? Is there a recommended method to verify bit-for-bit parity without performing a full data re-scan?