<?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: Unable to Analyze External Delta tables due to failed to initialize filesystem in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/unable-to-analyze-external-delta-tables-due-to-failed-to/m-p/82549#M36676</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/115160"&gt;@RobCox&lt;/a&gt;,&amp;nbsp;This might be due to incorrect configuration settings or insufficient permissions. Ensure that the &lt;CODE&gt;fs.azure.account.key&lt;/CODE&gt; configuration is accurate and that the service principal or identity running the command has the necessary permissions. The &lt;CODE&gt;ANALYZE TABLE&lt;/CODE&gt; command is essential for optimizing query plans by collecting statistics, which helps the optimizer effectively use features like Z-Ordering and Liquid Clustering.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Aug 2024 12:14:22 GMT</pubDate>
    <dc:creator>Retired_mod</dc:creator>
    <dc:date>2024-08-09T12:14:22Z</dc:date>
    <item>
      <title>Unable to Analyze External Delta tables due to failed to initialize filesystem</title>
      <link>https://community.databricks.com/t5/data-engineering/unable-to-analyze-external-delta-tables-due-to-failed-to/m-p/82203#M36553</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I've recently noticed we've never been using Analyze Table, after doing z-ordering / liquid clustering investigations and noticing the query plans for our delta tables were not considering these paths.&lt;/P&gt;&lt;P&gt;I'm trying to execute the following command to trigger statistics for our delta tables&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;spark.sql(f"ANALYZE TABLE delta.my_table_path COMPUTE DELTA STATISTICS") (my_table_path is backticked)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;my_table_path is an&amp;nbsp;&lt;STRONG&gt;abfss path&lt;/STRONG&gt;, we are not&amp;nbsp;using unity catalogue currently.&lt;/P&gt;&lt;P&gt;The error being received is&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;WARN FileSystem: Failed to initialize filesystem my_table_path: Failure to initialize configuration for storage account XXXXXXXX.dfs.core.windows.net: Invalid configuration value detected for fs.azure.account.keyInvalid configuration value detected for fs.azure.account.key&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, we can successfully run commands against this table path such as&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;spark.sql(f"DESCRIBE DETAIL delta.my_table_path").show()&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In addition to this reading/writing/doing optimize are also all working, and I was able to deep clone the source data to this location in order to do all this testing.&lt;/P&gt;&lt;P&gt;Does anyone know what might be at play here? Does Analyze use some elevated permissions on the blob storage that we're running into for example?&lt;/P&gt;&lt;P&gt;In addition to this, I believe running the Analyze command is key to not seeing our execution plans be optimized to use z-ordering or liquid clustering, is this a correct assumption? Currently the execution plan ignores all of these despite doing optimize operations.&lt;/P&gt;&lt;P&gt;Thanks in advance if you're able to look at this!&lt;/P&gt;</description>
      <pubDate>Wed, 07 Aug 2024 12:37:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/unable-to-analyze-external-delta-tables-due-to-failed-to/m-p/82203#M36553</guid>
      <dc:creator>RobCox</dc:creator>
      <dc:date>2024-08-07T12:37:56Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to Analyze External Delta tables due to failed to initialize filesystem</title>
      <link>https://community.databricks.com/t5/data-engineering/unable-to-analyze-external-delta-tables-due-to-failed-to/m-p/82549#M36676</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/115160"&gt;@RobCox&lt;/a&gt;,&amp;nbsp;This might be due to incorrect configuration settings or insufficient permissions. Ensure that the &lt;CODE&gt;fs.azure.account.key&lt;/CODE&gt; configuration is accurate and that the service principal or identity running the command has the necessary permissions. The &lt;CODE&gt;ANALYZE TABLE&lt;/CODE&gt; command is essential for optimizing query plans by collecting statistics, which helps the optimizer effectively use features like Z-Ordering and Liquid Clustering.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Aug 2024 12:14:22 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/unable-to-analyze-external-delta-tables-due-to-failed-to/m-p/82549#M36676</guid>
      <dc:creator>Retired_mod</dc:creator>
      <dc:date>2024-08-09T12:14:22Z</dc:date>
    </item>
  </channel>
</rss>

