Connector Improvement: Separate BigQuery connector name from destination schema prefix
Answered
We have several BigQuery datasets that we would like to sync to a Cloud SQL Postgres database. I see it is recommended to set up a separate connector for each dataset. However, the connector ID is used as a prefix to the Postgres schema name, which makes the schema names unwieldy. For example, if I have a dataset "my_data" and I use that as the prefix, the Postgres schema comes out as "my_data_my_data".
Ideally:
- There would be a separate field for the connector name
- The prefix would be optional, so the BigQuery dataset name could match the Postgres schema name
-
Official comment
Hi John,
Thank you for your feature request. After thorough consideration, we have determined that this proposal does not align with our current product development framework. Our strategy is to focus on core use cases where Fivetran can provide distinct value. We appreciate your input and will continue to assess interest in this area as we move forward.
Best Regards,
Please sign in to leave a comment.
Comments
1 comment