The Fivetran Platform connector will soon be seeing a few updates which will result in breaking changes for new connectors. The breaking changes include:
The connector_id field in the incremental_mar table will be renamed to connector_name.
We currently rename this field already in the stg_fivetran_platform__incremental_mar model. Therefore, we will need to update this to ensure backwards and future compatibility following this connector update.
The connector table will be renamed to connection.
Additionally, the connection table PK will change id (previously connector_id) along with renaming changes to FK (will now be connection_id) references. The other tables with FK renaming which this data model leverages include:
incremental_mar
log
Describe alternatives you've considered
No response
Are you interested in contributing this feature?
[ ] Yes.
[ ] Yes, but I will need assistance and will schedule time during your office hours for guidance.
[ ] No.
Anything else?
For existing connectors, this won't technically be breaking as both the old and new versions of the fields/tables will be generated. However, we will want to make sure the data model is updated to reflect the new changes while also being backwards compatible.
Please reference the internal ticket for additional details around these upcoming changes.
Is there an existing feature request for this?
Describe the Feature
The Fivetran Platform connector will soon be seeing a few updates which will result in breaking changes for new connectors. The breaking changes include:
connector_id
field in the incremental_mar table will be renamed toconnector_name
.id
(previouslyconnector_id
) along with renaming changes to FK (will now beconnection_id
) references. The other tables with FK renaming which this data model leverages include:Describe alternatives you've considered
No response
Are you interested in contributing this feature?
Anything else?
For existing connectors, this won't technically be breaking as both the old and new versions of the fields/tables will be generated. However, we will want to make sure the data model is updated to reflect the new changes while also being backwards compatible.
Please reference the internal ticket for additional details around these upcoming changes.