<?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: Invalid configuration value detected for fs.azure.account.key only when trying to save RDD in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/invalid-configuration-value-detected-for-fs-azure-account-key/m-p/50190#M28727</link>
    <description>&lt;P&gt;I will post here what worked resolving this error for us, in case someone else in the future encounters this.&lt;/P&gt;&lt;P&gt;It turns out that this error appears in this case, when we were using the below command while the directory '&lt;STRONG&gt;staging2&lt;/STRONG&gt;' already exists. To avoid this error, the '&lt;STRONG&gt;staging2&lt;/STRONG&gt;' directory has to be deleted before attempting to use '&lt;STRONG&gt;saveAsTextFile&lt;/STRONG&gt;'.&lt;/P&gt;&lt;LI-CODE lang="python"&gt;rdd_processed.saveAsTextFile(path+'/staging2/')&lt;/LI-CODE&gt;&lt;P&gt;The weird thing is that we were already doing that, but we would still get the error. We had a notebook cell that deletes the path ''&lt;STRONG&gt;path+'/staging2/'&lt;/STRONG&gt;", and then on the next cell, the above command would run, giving the error.&lt;/P&gt;&lt;P&gt;It turns out, to address this, the delete command of the path has to be on the same exact cell as the '&lt;STRONG&gt;saveAsText&lt;/STRONG&gt;' line of code. When we put the code in the same cell, the error wouldn't show anymore and the saving of the &lt;STRONG&gt;rdd_processed&lt;/STRONG&gt; was successful. This is definitely a bug as it doesn't make sense why it works, but for now at least there's a solution.&lt;/P&gt;</description>
    <pubDate>Tue, 31 Oct 2023 12:42:00 GMT</pubDate>
    <dc:creator>pavlos_skev</dc:creator>
    <dc:date>2023-10-31T12:42:00Z</dc:date>
    <item>
      <title>Invalid configuration value detected for fs.azure.account.key only when trying to save RDD</title>
      <link>https://community.databricks.com/t5/data-engineering/invalid-configuration-value-detected-for-fs-azure-account-key/m-p/49920#M28650</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We have encountered a weird issue in our (old) set-up that looks like a bug in the Unity Catalog. The storage account which we are trying to persist is configured via External Volumes.&lt;/P&gt;&lt;P&gt;We have a pipeline that gets XML data and stores it in an RDD. The code then attempts to save the RDD, which causes the error:&amp;nbsp;Invalid configuration value detected for fs.azure.account.key.&lt;/P&gt;&lt;P&gt;The weird thing is that this only happens when attempting to persist the RDD, but when attempting to persist a DataFrame, there is no issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;path = 'abfss://......'
df = dummyDataframe()
# rdd_processed.collect() -&amp;gt; ['xml content 1', 'xml content 2', ..., 'xml content n']

df.write.text(path+'/staging1/') # works like a charm, can view saved files in SA
rdd_processed.saveAsTextFile(path+'/staging2/') # returns the error&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Oct 2023 12:18:25 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/invalid-configuration-value-detected-for-fs-azure-account-key/m-p/49920#M28650</guid>
      <dc:creator>pavlos_skev</dc:creator>
      <dc:date>2023-10-26T12:18:25Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid configuration value detected for fs.azure.account.key only when trying to save RDD</title>
      <link>https://community.databricks.com/t5/data-engineering/invalid-configuration-value-detected-for-fs-azure-account-key/m-p/50182#M28724</link>
      <description>&lt;P&gt;Hello Kaniz,&lt;/P&gt;&lt;P&gt;Something that I forgot to mention in the OP, is that we are using Unity Catalog volumes to connect to the storage account, that are tested and work properly. I found the solution which seems like a major bug, unless I am missing something. I will post my answer in another comment. Thanks for reaching out.&lt;/P&gt;</description>
      <pubDate>Tue, 31 Oct 2023 09:40:25 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/invalid-configuration-value-detected-for-fs-azure-account-key/m-p/50182#M28724</guid>
      <dc:creator>pavlos_skev</dc:creator>
      <dc:date>2023-10-31T09:40:25Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid configuration value detected for fs.azure.account.key only when trying to save RDD</title>
      <link>https://community.databricks.com/t5/data-engineering/invalid-configuration-value-detected-for-fs-azure-account-key/m-p/50190#M28727</link>
      <description>&lt;P&gt;I will post here what worked resolving this error for us, in case someone else in the future encounters this.&lt;/P&gt;&lt;P&gt;It turns out that this error appears in this case, when we were using the below command while the directory '&lt;STRONG&gt;staging2&lt;/STRONG&gt;' already exists. To avoid this error, the '&lt;STRONG&gt;staging2&lt;/STRONG&gt;' directory has to be deleted before attempting to use '&lt;STRONG&gt;saveAsTextFile&lt;/STRONG&gt;'.&lt;/P&gt;&lt;LI-CODE lang="python"&gt;rdd_processed.saveAsTextFile(path+'/staging2/')&lt;/LI-CODE&gt;&lt;P&gt;The weird thing is that we were already doing that, but we would still get the error. We had a notebook cell that deletes the path ''&lt;STRONG&gt;path+'/staging2/'&lt;/STRONG&gt;", and then on the next cell, the above command would run, giving the error.&lt;/P&gt;&lt;P&gt;It turns out, to address this, the delete command of the path has to be on the same exact cell as the '&lt;STRONG&gt;saveAsText&lt;/STRONG&gt;' line of code. When we put the code in the same cell, the error wouldn't show anymore and the saving of the &lt;STRONG&gt;rdd_processed&lt;/STRONG&gt; was successful. This is definitely a bug as it doesn't make sense why it works, but for now at least there's a solution.&lt;/P&gt;</description>
      <pubDate>Tue, 31 Oct 2023 12:42:00 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/invalid-configuration-value-detected-for-fs-azure-account-key/m-p/50190#M28727</guid>
      <dc:creator>pavlos_skev</dc:creator>
      <dc:date>2023-10-31T12:42:00Z</dc:date>
    </item>
  </channel>
</rss>

