Connector Improvement: Deselecting child tables from schema
AnsweredHi Fivetran Product Team,
When reviewing the usage metrics for our Fivetran connector, I noticed that a significant number of MARs (Monthly Active Rows) are being charged for entities we’re not actively pulling data from. For example, the line_stop entity shows approximately 1.5 million MARs, despite us not selecting any fields from it. However, I do see that the primary key is still being synced.
It would be great if you could allow deselection of chile tables in the Fivetran connector. It seems unreasonable to incur MAR charges for entities that aren't being loaded into our destination.
Thanks,
Ari Johannesson
-
Official comment
Hi Ari,
Thanks for submitting this request. This feature—the ability to deselect any child tables from a connector schema—is currently in development. The reason you are still seeing MAR for a table is you cannot de-select all fields in the table (the primary keys are not de-selectable) and the table isn't de-selectable because the data for it is fetched when we fetch the data for the parent table.
We are currently working on removing these restrictions, and will keep you updated here.Thanks,
Shiva
Please sign in to leave a comment.
Comments
1 comment