We are experiencing issues with the connectors in their Fivetran integration.
We have configured the connectors to block all schema changes, but they are still seeing new column names being created in the schema, although they remain unchecked.

Also, we are not receiving email notifications for the introduction of new data a second time when the same blocked schema is pushed again. We are concerned that if these columns are included again in future CSV files, we will not receive a new schema notification.

We request a feature enhancement to ensure that blocked columns are not logically included in the schema unless explicitly allowed, making the functionality more robust and not limited to one-time use.

Feature Request: Improve schema change blocking functionality in Fivetran connectors

Details:

• Currently, even with the blocking of all schema changes enabled, new column names are being added to the schema, albeit unchecked.
• Email notifications for new data introductions are not being received the second time and so on,
• Concerns about the potential repetition of blocked columns in future CSV files without triggering a new schema notification.
• Suggestion to enhance the functionality:
  1. Blocked columns should not be logically included in the schema unless explicitly allowed.
  2. Ensure that new column names, which are blocked, do not appear in the schema even if they are present in the data source.
  3. Address the issue of missing email notifications for new data introductions.
     
     
• This enhancement would make the schema change blocking feature more reliable and prevent blocked columns from affecting the schema in subsequent data updates.
• By implementing this improvement, the functionality would not be limited to one-time use, providing better control and stability for managing schema changes in Fivetran connectors.

Thanks