<?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: Schema Evolution in Azure databricks in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/schema-evolution-in-azure-databricks/m-p/105509#M42162</link>
    <description>&lt;P&gt;For these scenarios, you can use &lt;A href="https://docs.databricks.com/en/delta/update-schema.html#update-delta-lake-table-schema" target="_self"&gt;schema evolution capabilities&lt;/A&gt; like mergeSchema or opt to use the new &lt;A href="https://docs.databricks.com/en/sql/language-manual/data-types/variant-type.html" target="_self"&gt;VariantType&lt;/A&gt;&amp;nbsp;to avoid requiring a schema at time of ingest.&lt;/P&gt;</description>
    <pubDate>Mon, 13 Jan 2025 22:03:39 GMT</pubDate>
    <dc:creator>cgrant</dc:creator>
    <dc:date>2025-01-13T22:03:39Z</dc:date>
    <item>
      <title>Schema Evolution in Azure databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/schema-evolution-in-azure-databricks/m-p/62258#M31936</link>
      <description>&lt;P class="lia-align-left"&gt;Hi All -&lt;BR /&gt;&lt;BR /&gt;In my scenario, Loading data from 100 of Json files.&lt;/P&gt;&lt;P class="lia-align-left"&gt;Problem is, fields/columns are missing when JSON file contains new fields.&lt;/P&gt;&lt;P class="lia-align-left"&gt;&lt;STRONG&gt;Full Load: &lt;/STRONG&gt;&lt;/P&gt;&lt;P class="lia-align-left"&gt;while writing JSON to delta use the option ("mergeschema", "true") so that we do not miss new columns&amp;nbsp;&lt;/P&gt;&lt;P class="lia-align-left"&gt;&lt;STRONG&gt;Incremental Load:&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="lia-align-left"&gt;Problem is here as schema does not match with existing schema.&lt;/P&gt;&lt;P class="lia-align-left"&gt;Could you please assist with schema&amp;nbsp;comparison&amp;nbsp;while doing incremental load.&lt;/P&gt;&lt;P class="lia-align-left"&gt;New JSON files schema should compare with existing JSON files schema.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Feb 2024 18:15:25 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/schema-evolution-in-azure-databricks/m-p/62258#M31936</guid>
      <dc:creator>CBL</dc:creator>
      <dc:date>2024-02-28T18:15:25Z</dc:date>
    </item>
    <item>
      <title>Re: Schema Evolution in Azure databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/schema-evolution-in-azure-databricks/m-p/105509#M42162</link>
      <description>&lt;P&gt;For these scenarios, you can use &lt;A href="https://docs.databricks.com/en/delta/update-schema.html#update-delta-lake-table-schema" target="_self"&gt;schema evolution capabilities&lt;/A&gt; like mergeSchema or opt to use the new &lt;A href="https://docs.databricks.com/en/sql/language-manual/data-types/variant-type.html" target="_self"&gt;VariantType&lt;/A&gt;&amp;nbsp;to avoid requiring a schema at time of ingest.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jan 2025 22:03:39 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/schema-evolution-in-azure-databricks/m-p/105509#M42162</guid>
      <dc:creator>cgrant</dc:creator>
      <dc:date>2025-01-13T22:03:39Z</dc:date>
    </item>
  </channel>
</rss>

