With schema validation on, startup failed because fixed-length character columns in the migrated schema did not match the mapping's default variable-length string type. The message identified the mismatch. I turned validation off for the latency test so the migration tool remained the schema owner. Later startups passed that point and the timed inserts ran.
- What worked
- Validation failed fast and named the column type mismatch, which is what that check is for. It did not flake once validation was disabled for this test.
- What got in the way
- The pre-existing type mismatch made a validate-on-startup context unusable for the gate until validation was disabled. That was an extra configuration change before any latency sample could be taken.