<?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: Genie Code hallucinates CLI commands in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/genie-code-hallucinates-cli-commands/m-p/160117#M54860</link>
    <description>&lt;P&gt;The command shown in the screenshot appears to be hallucinated.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;databricks sql-statements execute&lt;/STRONG&gt; is not a valid Databricks CLI command. It looks like Genie combined concepts from the SQL Statement Execution API with CLI syntax that doesn't actually exist.&lt;/P&gt;&lt;P&gt;This is one of the areas where I'd strongly recommend validating generated CLI commands against the official documentation before relying on them.&lt;/P&gt;&lt;P&gt;If your goal is to execute SQL programmatically, the supported options are:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;SQL Statement Execution API&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Databricks SDK (&lt;STRONG&gt;statement_execution.execute_statement(...)&lt;/STRONG&gt;)&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Databricks SQL Connector for Python&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;spark.sql(...)&lt;/STRONG&gt; if you're already running on Databricks compute&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;For example, using the Statement Execution API:&lt;/P&gt;&lt;PRE&gt;databricks api post /api/2.0/sql/statements --json '{
  "warehouse_id": "&amp;lt;warehouse-id&amp;gt;",
  "statement": "SHOW SCHEMAS IN customer360"
}'&lt;/PRE&gt;&lt;P&gt;The screenshot is a good example of why AI-generated commands should be verified before use—everything about the syntax looks plausible even though the command group itself doesn't exist.&lt;/P&gt;</description>
    <pubDate>Mon, 22 Jun 2026 12:32:44 GMT</pubDate>
    <dc:creator>Yogasathyandrun</dc:creator>
    <dc:date>2026-06-22T12:32:44Z</dc:date>
    <item>
      <title>Genie Code hallucinates CLI commands</title>
      <link>https://community.databricks.com/t5/data-engineering/genie-code-hallucinates-cli-commands/m-p/160104#M54859</link>
      <description>&lt;P&gt;I want to run some SQL commands programmatically against and decided to use Genie Code to help me, it came up with unsupported and non-existent commands.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="genie_0-1782127873093.png" style="width: 400px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/28133iF7E6EF2B56E1DE6E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="genie_0-1782127873093.png" alt="genie_0-1782127873093.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jun 2026 11:31:26 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/genie-code-hallucinates-cli-commands/m-p/160104#M54859</guid>
      <dc:creator>genie</dc:creator>
      <dc:date>2026-06-22T11:31:26Z</dc:date>
    </item>
    <item>
      <title>Re: Genie Code hallucinates CLI commands</title>
      <link>https://community.databricks.com/t5/data-engineering/genie-code-hallucinates-cli-commands/m-p/160117#M54860</link>
      <description>&lt;P&gt;The command shown in the screenshot appears to be hallucinated.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;databricks sql-statements execute&lt;/STRONG&gt; is not a valid Databricks CLI command. It looks like Genie combined concepts from the SQL Statement Execution API with CLI syntax that doesn't actually exist.&lt;/P&gt;&lt;P&gt;This is one of the areas where I'd strongly recommend validating generated CLI commands against the official documentation before relying on them.&lt;/P&gt;&lt;P&gt;If your goal is to execute SQL programmatically, the supported options are:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;SQL Statement Execution API&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Databricks SDK (&lt;STRONG&gt;statement_execution.execute_statement(...)&lt;/STRONG&gt;)&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Databricks SQL Connector for Python&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;spark.sql(...)&lt;/STRONG&gt; if you're already running on Databricks compute&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;For example, using the Statement Execution API:&lt;/P&gt;&lt;PRE&gt;databricks api post /api/2.0/sql/statements --json '{
  "warehouse_id": "&amp;lt;warehouse-id&amp;gt;",
  "statement": "SHOW SCHEMAS IN customer360"
}'&lt;/PRE&gt;&lt;P&gt;The screenshot is a good example of why AI-generated commands should be verified before use—everything about the syntax looks plausible even though the command group itself doesn't exist.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jun 2026 12:32:44 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/genie-code-hallucinates-cli-commands/m-p/160117#M54860</guid>
      <dc:creator>Yogasathyandrun</dc:creator>
      <dc:date>2026-06-22T12:32:44Z</dc:date>
    </item>
  </channel>
</rss>

