Migration engine to detect table schema (DDL) changes and apply them to target (according to configured preference at multiple levels - System/DB/Table)

[shaneelprasad]

The migration engine continuously runs as a systemd service and migrates full tables (or deltas from Netezza). This process fails when the source and target table schemas don't match.

Can the engine detect these changes and then act according to the following configurable options:

• Drop and recreate target table followed by a full sync
• Do nothing and report failed

These options need to be configurable at the following levels:

• Specific tables
• Defaults for all tables in the current database/job