Schema verification changed so it fails only if table columns has been changed
Schema verification code, even worked correctly, was too strict and disallow to restart replaying HAF instance (interrupted while replaying) in case when it entered massive sync and dropped FKs and indexes. Then schema verifier reported differences (missing constraints and indexes) and prevent another startup. This change are relaxing schema verification rules, to control only pure table schema (columns) changes.
Edited by Bartek Wrona