Hello muaaz !

I don't think that's the best pattern to follow and I recommend you to avoid registering tables directly from gs://... paths and instead put the data under a UC external location backed by a storage credential. When I check the doc, the best way is that external table paths should live inside an existing external location and it is better organizing this as one external location per schema for external table use cases.

Best case scenario is also to use managed tables by default unless you specifically need in place access to existing data or direct access from non Databricks tools.

So try :

with that location living inside a precreated UC external location such as:

CREATE EXTERNAL LOCATION ext_schema_name
URL 'gs://my-bucket/external/schema_name/'
WITH (STORAGE CREDENTIAL gcs_credential);

https://docs.databricks.com/gcp/en/connect/unity-catalog/cloud-storage