Currently the transformation and trigger models are used for basic SQL transformations. However, these have since been deprecated in the Fivetran platform. Therefore, there is no need for these tables to be pulled through as staging models or through the transformations status end model.
Upon it's removal we will be able to rely on the log table to generate all status' for Fivetran dbt orchestrated transformations.
Describe alternatives you've considered
No response
Are you interested in contributing this feature?
[X] Yes.
[ ] Yes, but I will need assistance and will schedule time during your office hours for guidance.
Is there an existing feature request for this?
Describe the Feature
Currently the
transformationandtriggermodels are used for basic SQL transformations. However, these have since been deprecated in the Fivetran platform. Therefore, there is no need for these tables to be pulled through as staging models or through the transformations status end model.Upon it's removal we will be able to rely on the
logtable to generate all status' for Fivetran dbt orchestrated transformations.Describe alternatives you've considered
No response
Are you interested in contributing this feature?
Anything else?
No response