You can enable this feature by setting Enable hard deletes for columns to true in your destination’s advanced settings.
For safety reasons, columns are not automatically dropped from destination tables since this operation is nearly irreversible. While some destinations support undos, we implement a strict safety check process:
When a column is deleted from the source, the first row that omits this column marks it for potential removal
We then monitor CDC events for 6 hours to ensure the column is consistently omitted
Only after this verification period will we proceed with dropping the column
This safety mechanism helps prevent accidental data loss and ensures the column is truly no longer needed.
We provide additional configuration options to give you more control over schema evolution:
Column Exclusion
Use column exclusion to prevent specific columns from being added to your destination. This is particularly useful for:
Excluding sensitive data columns (e.g., PII, passwords)
Preventing unnecessary columns from being synced
Managing storage costs by excluding large or unused columns
To use this feature, simply specify the columns you want to exclude in your table’s advanced settings.
Column Inclusion
Column inclusion allows you to explicitly define which columns should be synced to your destination. This feature:
Gives you complete control over your destination schema
Helps maintain a clean, minimal dataset
Requires manual management of new columns
Column inclusion is mutually exclusive with column exclusion. When using this feature, you’ll need to manually add any new columns to your destination schema as they appear in the source.