Table shared via Delta sharingschema not shown in Unity-Catalog

[Maaax]

Hello dear community,

I use the following command to register the provider including shares to unity-catalog:

databricks unity-catalog create-provider --name company --recipient-profile-json-file ~/Develop/profile.json

Once it is registered, I could see the provider and shares in the unity-catalog delta sharing panel. On each of the share I could click on "create catalog" to import the schema to unity-catalog.

I could see the created catalog, schema and table in unity-catalog. But when I click on the table to see its schema, I see the following error:

Failed to request /ajax-api/2.1/unity-catalog/tables/company.patient_schema2.patient_table2?include_browse=true: 404 Not Found Schema 'company.patient_schema2' does not exist.

I have not seen similar error before. Anyone has an idea where could potentially cause the error? Thanks.

[Kaniz]

Hi @Maaax, It appears that you’re encountering an error related to the Unity Catalog in Databricks. 

Let’s explore some potential causes and solutions:

Schema and Catalog Verification:

• Verify the spelling and correctness of the schema and catalog names. Ensure that you’ve qualified the name with the correct schema and catalog.
• You can use the current_schema() output to verify the current schema context or explicitly qualify t....

Catalog Location Configuration:

• Unity Catalog allows you to set a location for catalogs. Make sure you’ve configured the correct location for your catalog.
• For example, you can create a catalog called “hr_prod” and assign the location abfss://mycompany-hr-....

Access Permissions:

• Ensure that the managed identity (Access Connector for Azure Databricks) has the necessary permissions:
  • Grant the “Storage Blob Data Reader” permission at the Storage Account level.
  • Grant the “Storage Blob Data Contributor” permission at the container level used by the workspace.
• Double-check that the managed identity has the appropriate permissions on the storage container.

Folder Structure Creation:

• You mentioned that the folder structure is created successfully for the Delta table. However, it fails when acquiring the SAS token.
• Confirm that the folder structure is consistent with the expected Unity Catalog structure.

Workspace Configuration:

• Ensure that your Databricks workspace configuration is correct:
  • The access connector is properly set up.
  • The metastore is bound to the DataLake.
  • You have the necessary permissions in the workspace.

Error Tolerance:

• To tolerate errors during table creation, consider using CREATE TABLE IF NOT EXISTS or DROP TABLE IF....

Remember to check each of these aspects carefully, and hopefully, you’ll be able to resolve the issue. 

[Kaniz]

Hey there! Thanks a bunch for being part of our awesome community! 🎉 

We love having you around and appreciate all your questions. Take a moment to check out the responses – you'll find some great info. Your input is valuable, so pick the best solution for you. And remember, if you ever need more help , we're here for you! 

Keep being awesome! 😊🚀