Hi Aleksandra,

Thanks for the reply. I have tried using a different catalog slot (for example glue_catalog) but this does not work in a workspace with unity catalog enabled - it does work in a non unity catalog workspace.

The only catalog slot that works is overriding spark_catalog. This seems to work in terms of allowing reads and writes to the tables however we are running into these slightly odd issues.

The central catalog is Glue, we are not even really using Unity Catalog at all. It was enabled when the workspace was created and now it doesn't seem to be possible to turn it off.

We are tied to the Glue catalog because or our Athena usage and we absolutely need write access from Databricks. Would we be better just creating a new workspace which doesn't have Unity Catalog enabled?

Kind regards