Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: adding extra metadata to destination

Planned
Howard Zhang User

A bit of thought on the fivetran metadata table (like the audit table) I think it will be helpful to have a PK/UK list table created in the Fivetran landing schema. DW like Snowflake supports PK constraints on the table but other vendors such as Databricks or Bigquery doesn’t. If there is a table read constraints information from the source or API and puts them in this table then it can be beneficial for the downstream transformation.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Meera User

    Hi Howard,

    This is currently available using our Metadata API. In the next two quarters, we will be releasing functionality to support PK/FK as part of our Fivetran log connector.

    Would you be willing to share how this information is likely to be used downstream? To ensure that the data lands in a way most useful to you, it would be extremely helpful to understand how the data is consumed downstream.

    Regards,

    Meera

  • IT Admin User

    Hi Meera:

    Thanks for the comment, I use dbt for the down stream process. If fivetran can save this information in the landing area, I can write a dbt marco to automatically generate dbt snapshot model. or even use python code to create pk test cases in the yaml file. 

    Thanks 

    Howard