Potential Unity Catalog Bug: Invalid configuration value detected for fs.azure.account.keyInvalid

[pavlos_skev]

Hello,

We are migrating to Unity Catalog (UC), and for very few of our tables, we get the below error when trying to write or even display them. We are using UC enabled clusters, usually with runtime versions 12.2 LTS. The below error, when it happens, it looks like it's a direct cause of the Runtime version (12.2 LTS), as switching to 10.4 LTS makes the code run successfully. 

The code reads some tables from catalog A, creates a new product table in Catalog B using the tables from catalog A, and lastly creates a transformed version of the product table and also saves it in Catalog B.

The error:

org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in stage 8.0 failed 4 times, most recent failure: Lost task 0.3 in stage 8.0 (TID 32) (10.128.200.145 executor 0): Failure to initialize configuration for storage account aaaaaaaaaaaa.dfs.core.windows.net: Invalid configuration value detected for fs.azure.account.keyInvalid configuration value detected for fs.azure.account.key

Has anyone encountered something similar in the past? If yes, please elaborate on what the underlying issue is, and what measures to take to avoid this in the future.

Thanks in advance for your time!

[User16539034020]

Hello, 

Thanks for contacting Databricks Support. 

The error message indicates a problem with the configuration key fs.azure.account.key. This configuration key is used to provide the access key for the Azure Data Lake Storage account. Not sure if this is the root cause here. Could you check the log4j for more error message? Thanks. 

Regards