Connector Improvement: Dropping blocked columns via endpoint
Answered
Creating this feature request as a result of this inquiry I previously had with Fivetran.
Currently the only way to remove a BLOCKED column is via the UI (screenshot attached). When deselecting a blocked column via the UI you are presented the option of dropping the blocked column, otherwise that column will be preserved in the destination and have all of its values set to NULL.
Our current solution uses the Fivetran PATCH https://api.fivetran.com/v1/connectors/{connector_id}/schemas API to make adjustments to the connector schema, but there is no way to opt to drop a blocked column in the destination instead of setting all of that column's values to null.
This feature request is to add support to the https://api.fivetran.com/v1/connectors/{connector_id}/schemas API for dropping a BLOCKED column from the destination if disabling a column. 
-
Official comment
Hey Phillip,
Thanks for taking the time to write such a clear feature request! How often would you need to do something like this? What kinds of use cases occur where you are programmatically adjusting schema downstream of earlier, schema defining syncs?
Thanks,
Jimmy
Please sign in to leave a comment.
Comments
1 comment