<?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 import of tables to a new metastore failed with schema mismatch &amp;quot;specified schema does not match the existing schema&amp;quot; in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/import-of-tables-to-a-new-metastore-failed-with-schema-mismatch/m-p/30847#M22412</link>
    <description>&lt;P&gt;The error i get when importing certain delta table is&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The specified schema does not match the existing schema at dbfs:/mnt/mart/tablename&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;however, when i check the metadata table in the old workspace and the exported file, they match. However, it seems that whatever the metadata is in the external location above is different. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The main difference is that the for many of the columns in dbfs:/mnt the column type is string while the metadata from the metastore shows varchar255.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone advise why there would be a difference and a way to resolve it&lt;/P&gt;</description>
    <pubDate>Mon, 26 Sep 2022 13:22:10 GMT</pubDate>
    <dc:creator>nbakh</dc:creator>
    <dc:date>2022-09-26T13:22:10Z</dc:date>
    <item>
      <title>import of tables to a new metastore failed with schema mismatch "specified schema does not match the existing schema"</title>
      <link>https://community.databricks.com/t5/data-engineering/import-of-tables-to-a-new-metastore-failed-with-schema-mismatch/m-p/30847#M22412</link>
      <description>&lt;P&gt;The error i get when importing certain delta table is&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The specified schema does not match the existing schema at dbfs:/mnt/mart/tablename&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;however, when i check the metadata table in the old workspace and the exported file, they match. However, it seems that whatever the metadata is in the external location above is different. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The main difference is that the for many of the columns in dbfs:/mnt the column type is string while the metadata from the metastore shows varchar255.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone advise why there would be a difference and a way to resolve it&lt;/P&gt;</description>
      <pubDate>Mon, 26 Sep 2022 13:22:10 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/import-of-tables-to-a-new-metastore-failed-with-schema-mismatch/m-p/30847#M22412</guid>
      <dc:creator>nbakh</dc:creator>
      <dc:date>2022-09-26T13:22:10Z</dc:date>
    </item>
    <item>
      <title>Re: import of tables to a new metastore failed with schema mismatch "specified schema does not match the existing schema"</title>
      <link>https://community.databricks.com/t5/data-engineering/import-of-tables-to-a-new-metastore-failed-with-schema-mismatch/m-p/30848#M22413</link>
      <description>&lt;P&gt;below is example error. however, in existing metadata i still see varchar 100 as the type.  &lt;/P&gt;&lt;P&gt;Specified metadata for field Percentage is different from existing schema:\n&amp;nbsp;Specified: {}\n&amp;nbsp;Existing:&amp;nbsp;{\"HIVE_TYPE_STRING\":\"varchar(100)\"}\n\nIf your intention is to keep the existing schema&lt;/P&gt;</description>
      <pubDate>Mon, 26 Sep 2022 13:39:09 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/import-of-tables-to-a-new-metastore-failed-with-schema-mismatch/m-p/30848#M22413</guid>
      <dc:creator>nbakh</dc:creator>
      <dc:date>2022-09-26T13:39:09Z</dc:date>
    </item>
  </channel>
</rss>

