Which connector?: MySQL Connector

Additional details: 

We would like to request support for handling DROP FOREIGN KEY DDL operations without triggering a full table re-sync.

Dropping foreign keys is an expected operation in our MySQL environment, especially for some large tables where foreign key constraints may be removed for performance reasons. Some of these tables are also actively synced through Fivetran.

Currently, a DROP FOREIGN KEY operation may trigger a full table re-sync, which can significantly increase sync latency for large tables and potentially impact other tables in the connector.

Ideally, Fivetran should be able to parse and handle DROP FOREIGN KEY as a schema change without requiring a historical re-sync, since dropping the constraint itself does not remove or modify the existing column data.

Expected Behavior:

ALTER TABLE <table_name> DROP FOREIGN KEY <foreign_key_name> should be handled without triggering a full table re-sync.

This would help avoid unnecessary re-syncs and reduce the risk of significant replication delays when foreign key constraints are removed from large tables.