<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Foreign key constraint in a dlt pipeline in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/foreign-key-constraint-in-a-dlt-pipeline/m-p/90615#M37963</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/117384"&gt;@Mario_D&lt;/a&gt;!&lt;/P&gt;&lt;P&gt;While primary &amp;amp; foreign key constraints are generally available in Databricks Runtime 15.2 and above, they are strictly &lt;STRONG&gt;informational only&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;This means that a primary key will not prevent duplicates from being added to a table and a foreign key does not require the referenced value to exist in another table.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.databricks.com/en/tables/constraints.html#declare-primary-key-and-foreign-key-relationships" target="_blank"&gt;https://docs.databricks.com/en/tables/constraints.html#declare-primary-key-and-foreign-key-relationships&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 16 Sep 2024 16:52:32 GMT</pubDate>
    <dc:creator>RCo</dc:creator>
    <dc:date>2024-09-16T16:52:32Z</dc:date>
    <item>
      <title>Foreign key constraint in a dlt pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/foreign-key-constraint-in-a-dlt-pipeline/m-p/89774#M37900</link>
      <description>&lt;P&gt;As primary/foreign key constraints are now supported/available in Databricks, how are foreign key constraints handled in a dlt pipeline, i.e if a foreign key constraint is violated, is the record logged as a data quality issue and still added to the target table?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 11:08:03 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/foreign-key-constraint-in-a-dlt-pipeline/m-p/89774#M37900</guid>
      <dc:creator>Mario_D</dc:creator>
      <dc:date>2024-09-13T11:08:03Z</dc:date>
    </item>
    <item>
      <title>Re: Foreign key constraint in a dlt pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/foreign-key-constraint-in-a-dlt-pipeline/m-p/89781#M37903</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/117384"&gt;@Mario_D&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;I don't think primary/foreign constraint are supported by DLT. At least I can't find anything in documentation. But you obtain same result using DLT expectations:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://learn.microsoft.com/en-us/azure/databricks/delta-live-tables/expectations#validate-row-counts-across-tables" target="_blank"&gt;Manage data quality with Delta Live Tables - Azure Databricks | Microsoft Learn&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 11:47:32 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/foreign-key-constraint-in-a-dlt-pipeline/m-p/89781#M37903</guid>
      <dc:creator>szymon_dybczak</dc:creator>
      <dc:date>2024-09-13T11:47:32Z</dc:date>
    </item>
    <item>
      <title>Re: Foreign key constraint in a dlt pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/foreign-key-constraint-in-a-dlt-pipeline/m-p/90615#M37963</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/117384"&gt;@Mario_D&lt;/a&gt;!&lt;/P&gt;&lt;P&gt;While primary &amp;amp; foreign key constraints are generally available in Databricks Runtime 15.2 and above, they are strictly &lt;STRONG&gt;informational only&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;This means that a primary key will not prevent duplicates from being added to a table and a foreign key does not require the referenced value to exist in another table.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.databricks.com/en/tables/constraints.html#declare-primary-key-and-foreign-key-relationships" target="_blank"&gt;https://docs.databricks.com/en/tables/constraints.html#declare-primary-key-and-foreign-key-relationships&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Sep 2024 16:52:32 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/foreign-key-constraint-in-a-dlt-pipeline/m-p/90615#M37963</guid>
      <dc:creator>RCo</dc:creator>
      <dc:date>2024-09-16T16:52:32Z</dc:date>
    </item>
  </channel>
</rss>

