<?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 Random error: At least one column must be specified for the table? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19076#M12733</link>
    <description>&lt;P&gt;I have the following code in a notebook.  It is randomly giving me the error, "At least one column must be specified for the table."  The error occurs (if at all it occurs) only on the first run after attaching to a cluster.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cluster details:&lt;/P&gt;&lt;P&gt;Summary&lt;/P&gt;&lt;P&gt;5-10 Workers&lt;/P&gt;&lt;P&gt;320-640&amp;nbsp;GB Memory40-80&amp;nbsp;Cores1 Driver&lt;/P&gt;&lt;P&gt;64&amp;nbsp;GB Memory,&amp;nbsp;8&amp;nbsp;Cores Runtime&lt;/P&gt;&lt;P&gt;10.4.x-scala2.12 Apache Spark 3.2.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="dbr-bug"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/1072i4A751AAD20D2F9D8/image-size/large?v=v2&amp;amp;px=999" role="button" title="dbr-bug" alt="dbr-bug" /&gt;&lt;/span&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;</description>
    <pubDate>Fri, 02 Dec 2022 17:25:59 GMT</pubDate>
    <dc:creator>Jujiro</dc:creator>
    <dc:date>2022-12-02T17:25:59Z</dc:date>
    <item>
      <title>Random error: At least one column must be specified for the table?</title>
      <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19076#M12733</link>
      <description>&lt;P&gt;I have the following code in a notebook.  It is randomly giving me the error, "At least one column must be specified for the table."  The error occurs (if at all it occurs) only on the first run after attaching to a cluster.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cluster details:&lt;/P&gt;&lt;P&gt;Summary&lt;/P&gt;&lt;P&gt;5-10 Workers&lt;/P&gt;&lt;P&gt;320-640&amp;nbsp;GB Memory40-80&amp;nbsp;Cores1 Driver&lt;/P&gt;&lt;P&gt;64&amp;nbsp;GB Memory,&amp;nbsp;8&amp;nbsp;Cores Runtime&lt;/P&gt;&lt;P&gt;10.4.x-scala2.12 Apache Spark 3.2.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="dbr-bug"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/1072i4A751AAD20D2F9D8/image-size/large?v=v2&amp;amp;px=999" role="button" title="dbr-bug" alt="dbr-bug" /&gt;&lt;/span&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;</description>
      <pubDate>Fri, 02 Dec 2022 17:25:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19076#M12733</guid>
      <dc:creator>Jujiro</dc:creator>
      <dc:date>2022-12-02T17:25:59Z</dc:date>
    </item>
    <item>
      <title>Re: Random error: At least one column must be specified for the table?</title>
      <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19077#M12734</link>
      <description>&lt;P&gt;Create a support request databricks might help you in this issue.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Dec 2022 09:03:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19077#M12734</guid>
      <dc:creator>Ajay-Pandey</dc:creator>
      <dc:date>2022-12-07T09:03:17Z</dc:date>
    </item>
    <item>
      <title>Re: Random error: At least one column must be specified for the table?</title>
      <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19078#M12735</link>
      <description>&lt;P&gt;The issue occurs randomly.  The challenge is to recreate the issue for the support team to look.  I am hoping that the folks who have experienced similar error, would comment, and then maybe the DBR folks would have something to investigate.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Dec 2022 16:39:36 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19078#M12735</guid>
      <dc:creator>Jujiro</dc:creator>
      <dc:date>2022-12-07T16:39:36Z</dc:date>
    </item>
    <item>
      <title>Re: Random error: At least one column must be specified for the table?</title>
      <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19079#M12736</link>
      <description>&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image.png"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/1057i636D4E4E7339C8FE/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;Do you found any solution? Same error with me as well when i run below line.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;spark.sql("DROP TABLE IF EXISTS tempdb.data_result");&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2022 12:20:12 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19079#M12736</guid>
      <dc:creator>Shan57</dc:creator>
      <dc:date>2022-12-28T12:20:12Z</dc:date>
    </item>
    <item>
      <title>Re: Random error: At least one column must be specified for the table?</title>
      <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19080#M12737</link>
      <description>&lt;P&gt;Sorry, no solution yet.  &lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2022 14:09:37 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19080#M12737</guid>
      <dc:creator>Jujiro</dc:creator>
      <dc:date>2022-12-28T14:09:37Z</dc:date>
    </item>
    <item>
      <title>Re: Random error: At least one column must be specified for the table?</title>
      <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19081#M12738</link>
      <description>&lt;P&gt;I tried reproducing the issue in Databricks notebook, using 10.4 cluster and ran a few times. Unfortunately couldn't reproduce the issue. It runs successfully during each run. What is the frequency of this intermittent issue?  If you re-run the command 10 times would it throw error once?  Still would recommend to file a support ticket , so that we can take a deeper look at this.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 17:53:24 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19081#M12738</guid>
      <dc:creator>mathan_pillai</dc:creator>
      <dc:date>2023-01-30T17:53:24Z</dc:date>
    </item>
    <item>
      <title>Re: Random error: At least one column must be specified for the table?</title>
      <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19082#M12739</link>
      <description>&lt;P&gt;Are you having multiple threads that runs this statements concurrently ? If so the race condition could cause this issue, when trying to update the metastore.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 18:11:52 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19082#M12739</guid>
      <dc:creator>mathan_pillai</dc:creator>
      <dc:date>2023-01-30T18:11:52Z</dc:date>
    </item>
    <item>
      <title>Re: Random error: At least one column must be specified for the table?</title>
      <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19083#M12740</link>
      <description>&lt;P&gt;If you simply want to get rid of the table, you can drop the table using hive client, as well&lt;/P&gt;&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/azure/databricks/kb/metastore/drop-table-corruptedmetadata" target="test_blank"&gt;https://learn.microsoft.com/en-us/azure/databricks/kb/metastore/drop-table-corruptedmetadata&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 18:19:35 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19083#M12740</guid>
      <dc:creator>mathan_pillai</dc:creator>
      <dc:date>2023-01-30T18:19:35Z</dc:date>
    </item>
    <item>
      <title>Re: Random error: At least one column must be specified for the table?</title>
      <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19084#M12741</link>
      <description>&lt;P&gt;So, basically, I have addressed the issue (for now) by putting the culprit statement in a try/catch block with a few retries.  The error still occurs but clears in the second retry.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 18:28:58 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19084#M12741</guid>
      <dc:creator>Jujiro</dc:creator>
      <dc:date>2023-01-30T18:28:58Z</dc:date>
    </item>
    <item>
      <title>Re: Random error: At least one column must be specified for the table?</title>
      <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19085#M12742</link>
      <description>&lt;P&gt;I am not using any threading at all.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 18:29:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19085#M12742</guid>
      <dc:creator>Jujiro</dc:creator>
      <dc:date>2023-01-30T18:29:49Z</dc:date>
    </item>
    <item>
      <title>Re: Random error: At least one column must be specified for the table?</title>
      <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19086#M12743</link>
      <description>&lt;P&gt;I just wanted to simplify the code for illustration purposes.  In my case the error occurs at the insert statement after the ALTER TABLE statement.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 18:31:28 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19086#M12743</guid>
      <dc:creator>Jujiro</dc:creator>
      <dc:date>2023-01-30T18:31:28Z</dc:date>
    </item>
    <item>
      <title>Re: Random error: At least one column must be specified for the table?</title>
      <link>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19087#M12744</link>
      <description>&lt;P&gt;Please check if this could help or not:&lt;/P&gt;&lt;P&gt;spark.databricks.delta.catalog.update.enabled false&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2023 01:21:51 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/random-error-at-least-one-column-must-be-specified-for-the-table/m-p/19087#M12744</guid>
      <dc:creator>Harold</dc:creator>
      <dc:date>2023-06-06T01:21:51Z</dc:date>
    </item>
  </channel>
</rss>

