<?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: DQX - datacontract cli in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/dqx-datacontract-cli/m-p/157570#M54591</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/65591"&gt;@seefoods&lt;/a&gt;,&lt;/P&gt;
&lt;P class="wnfdntf _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea" data-pm-slice="1 3 []"&gt;Just came across this post. In case you are still looking for an answer, I see these as complementary rather than overlapping tools.&lt;/P&gt;
&lt;P&gt;A practical approach would be to keep the data contract as the source of truth in datacontract.yaml, use the &lt;A href="https://gpt.datacontract.com/sources/cli.datacontract.com/" rel="noopener noreferrer nofollow" target="_blank"&gt;Data Contract CLI docs&lt;/A&gt; for linting, testing, and contract evolution in CI/CD, and then use DQX inside Databricks for runtime enforcement, profiling, dashboards, and richer Spark-native quality checks.&lt;/P&gt;
&lt;P&gt;The nice connection point is that Data Contract CLI can export contracts to odcs, and DQX now has a public guide for &lt;A href="https://databrickslabs.github.io/dqx/docs/guide/data_contract_quality_rules_generation" rel="noopener noreferrer nofollow" target="_blank"&gt;data contract quality rule generation&lt;/A&gt;, which makes it a good fit for turning contract definitions into Databricks-side validation rules.&lt;/P&gt;
&lt;P class="wnfdntf _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;So the pattern I would suggest is:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Define and version the contract in datacontract.yaml.&lt;/LI&gt;
&lt;LI&gt;Run datacontract lint, datacontract test, and datacontract breaking in CI/CD.&lt;/LI&gt;
&lt;LI&gt;Export to ODCS if needed.&lt;/LI&gt;
&lt;LI&gt;Use DQX in Databricks to execute the operational quality checks close to the data.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="p1"&gt;&lt;FONT size="2" color="#FF6600"&gt;&lt;STRONG&gt;&lt;I&gt;If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.&lt;/I&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;I&gt;&lt;/I&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 24 May 2026 18:05:59 GMT</pubDate>
    <dc:creator>Ashwin_DSA</dc:creator>
    <dc:date>2026-05-24T18:05:59Z</dc:date>
    <item>
      <title>DQX - datacontract cli</title>
      <link>https://community.databricks.com/t5/data-engineering/dqx-datacontract-cli/m-p/134248#M50064</link>
      <description>&lt;P&gt;Hello Guyz,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Someone can i combine dqx databricks rules check with datacontract cli ? If yes can we share your idea?&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://gpt.datacontract.com/sources/cli.datacontract.com/" target="_blank"&gt;https://gpt.datacontract.com/sources/cli.datacontract.com/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Cordially,&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Oct 2025 16:28:03 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dqx-datacontract-cli/m-p/134248#M50064</guid>
      <dc:creator>seefoods</dc:creator>
      <dc:date>2025-10-08T16:28:03Z</dc:date>
    </item>
    <item>
      <title>Re: DQX - datacontract cli</title>
      <link>https://community.databricks.com/t5/data-engineering/dqx-datacontract-cli/m-p/157570#M54591</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/65591"&gt;@seefoods&lt;/a&gt;,&lt;/P&gt;
&lt;P class="wnfdntf _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea" data-pm-slice="1 3 []"&gt;Just came across this post. In case you are still looking for an answer, I see these as complementary rather than overlapping tools.&lt;/P&gt;
&lt;P&gt;A practical approach would be to keep the data contract as the source of truth in datacontract.yaml, use the &lt;A href="https://gpt.datacontract.com/sources/cli.datacontract.com/" rel="noopener noreferrer nofollow" target="_blank"&gt;Data Contract CLI docs&lt;/A&gt; for linting, testing, and contract evolution in CI/CD, and then use DQX inside Databricks for runtime enforcement, profiling, dashboards, and richer Spark-native quality checks.&lt;/P&gt;
&lt;P&gt;The nice connection point is that Data Contract CLI can export contracts to odcs, and DQX now has a public guide for &lt;A href="https://databrickslabs.github.io/dqx/docs/guide/data_contract_quality_rules_generation" rel="noopener noreferrer nofollow" target="_blank"&gt;data contract quality rule generation&lt;/A&gt;, which makes it a good fit for turning contract definitions into Databricks-side validation rules.&lt;/P&gt;
&lt;P class="wnfdntf _1ibi0s3f5 _1ibi0s3ce _1ibi0s3ea"&gt;So the pattern I would suggest is:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Define and version the contract in datacontract.yaml.&lt;/LI&gt;
&lt;LI&gt;Run datacontract lint, datacontract test, and datacontract breaking in CI/CD.&lt;/LI&gt;
&lt;LI&gt;Export to ODCS if needed.&lt;/LI&gt;
&lt;LI&gt;Use DQX in Databricks to execute the operational quality checks close to the data.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="p1"&gt;&lt;FONT size="2" color="#FF6600"&gt;&lt;STRONG&gt;&lt;I&gt;If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.&lt;/I&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;I&gt;&lt;/I&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 24 May 2026 18:05:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dqx-datacontract-cli/m-p/157570#M54591</guid>
      <dc:creator>Ashwin_DSA</dc:creator>
      <dc:date>2026-05-24T18:05:59Z</dc:date>
    </item>
  </channel>
</rss>

