GitHub Actions workflow cannot find the Databricks Unity Catalog and its tables
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
Context: Running the train_model_py.py file stored in Databricks through GitHub Actions. The notebook reads the Unity Catalog tables for pre-processing and works fine when run through the Databricks UI. However, it gives an error when run through GitHub Actions.
Setup Details:
- Serverless compute on the Free-Tier Databricks workspace. More info is in the Readme.md of this repo.
Resolutions Tried:
- Verified that the Host URL and Personal Access Token are as per the Databricks documentation.
- Verified that Unity Catalog is enabled for the workspace.
- Verified that Free-Tier serverless compute by default allows Unity Catalog.
- Explicitly granted permission to my email address and personal tokens.
- Explicitly set up and enabled Unity Catalog in the notebook.
- Tried providing the fully qualified table name (catalog.schema.tablename), but it generates a namespace error, i.e., it expects two-part names.
Interesting Observation:
Upon further investigation, I found that the GitHub Actions workflow can find the traditional Hive metastore (a.k.a. spark_catalog) tables. This is strange because I do not see this catalog or tables in the Databricks UI.
I want to be able to access the Unity Catalog and its tables when I run the file through the GitHub Actions workflow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday
Hi @sagarb,
It sounds like a permission issue or setup issue... what is the error you are hitting?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sunday - last edited Sunday
Since it doesn't recognize the catalog, it says unexpected word or extra word. 'workspace' is my unity catalog name. See below:
Error:
I also printed what catalogs and schemas it can see. This is the output I got in the GitHub Actions output:

