Connector Improvement: Provide more control over Dataset naming in Destinations
We'd like to see the connector name separated from the destination schema name to provide more consistency to our environments.
The issue we currently face is we give the connector a meaningful name for the fivetran interface something like <source>_<env> but theres no guarantee this name is meaningful in the destination which can lead to development challenges where we need to have dynamic variables building dataset names out of multi part naming due to fivetran creating datasets as <connector_name>_<source_schema>
-
It will be great if Fivetran can sort this out. We have similar issue around naming.
Please sign in to leave a comment.
Comments
1 comment