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

Community

Destination Improvement: Add primary/foreign key constraints to Databricks tables

Planned
Keith van der Meulen User

Fivetran connectors schemas list which columns are primary keys and foreign keys. However, these constraints are not added to the Databricks destination tables. I would love the tables in Databricks to have the constraints as part of the DDL so that I can use this metadata for downstream programs/operations.

For instance:

  • Primary key can be programmatically retrieved from the INFORMATION_SCHEMA on Fivetran catalogs can help with downstream MERGE INTO logic.
  • Foreign keys can be very useful for creating ERDs, like PowerBI suggesting joins based on column relationships. 

 

Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Egidio Terra Fivetranner
    Hi Keith,

    Thank you so much for sharing your feedback and highlighting the need for primary/foreign key constraints support in Databricks destinations! We know how valuable this capability is for many use cases.

    Great news—this feature is currently under development. We'll be sure to keep this thread updated with further announcements as we move closer to a general release. Thanks again for helping us make Fivetran better!

    Best regards,
    Egidio Terra